Loading...
Loading...
Found 759 Skills
Receive and process code review feedback effectively. Applies suggestions, addresses comments, and iterates on implementation improvements.
Apply feedback and implement review suggestions. Incorporates reviewer comments into code changes systematically.
Request peer review with proper context and preparation. Structures review requests with clear description of changes and testing status.
ALWAYS use this skill when creating or updating pull requests — never create or edit a PR directly without it. Follows Sentry conventions for PR titles, descriptions, and issue references. Trigger on any create PR, open PR, submit PR, make PR, update PR title, update PR description, edit PR, push and create PR, prepare changes for review task, or request for a PR writer.
Coding conventions enforcement agent. Auto-invoked when writing new code, reviewing code quality, adding headers, or checking documentation compliance across Python, TypeScript/JavaScript, and C#/.NET.
Perform structured code review and kanban transitions for completed task
Use this skill for multi-model AI code review. Trigger whenever the user asks to review code changes, audit a diff, check code quality, review a PR, review commits, or review uncommitted changes before pushing or merging. Also trigger when they say 'code review', 'review my changes', 'check this before I merge', or want multiple perspectives on code. Runs Codex and Claude reviews in parallel, then synthesizes a unified report. Do NOT use for reviewing documentation, markdown, or non-code files, or for trivial single-line changes.
Architect/CR agent role. Receives git diff, task spec, ADRs, design doc, and project conventions. Reviews code and returns APPROVED or CHANGES_REQUIRED. Do NOT invoke directly — dispatched by team-execute.
This skill should be used when the user asks to "analyze skill quality", "evaluate this skill", "review skill quality", "check my skill", or "generate quality report". Evaluates local skills across description quality, content organization, writing style, and structural integrity.
Prepare branch for code review by building context, identifying issues, and suggesting improvements
Review changes for test gaps, simplification, naming consistency, reuse opportunities, and TODO quality
Generate manual test plans for PR changes with verified commands and pass/fail criteria