// Review code changes (diffs, PRs, patches) and provide structured, actionable feedback on correctness, maintainability, and test coverage. Use when the user asks for a code review, requests feedback on a patch/PR, or wants an assessment of changes.
Automatic quality control, linting, and static analysis procedures. Use when validating code changes for syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis.
Refactoring and cleanup - improving code structure, removing dead code, eliminating duplication, or pre-merge cleanup. Use when code is hard to maintain, has dead code or debug artifacts, or needs pre-merge polishing.
Fix a GitHub issue end-to-end - from reading the issue, understanding requirements, implementing the fix, writing tests, and creating a commit. Use when given a GitHub issue number or URL to resolve.
Optimize code for readability, performance, maintainability, and security across Bash, Python, and Rust. Use when asked to improve code quality, optimize performance, add type safety, or refactor for idioms.
Create, debug, and optimize GitHub Actions workflows with security best practices. Use when asked to "create workflow", "fix workflow", "add CI", or needs help with GitHub Actions.
Craft immersive, high-performance premium web experiences with advanced motion, typography, and architectural craftsmanship. Use when building award-level landing pages, interactive portfolios, or components requiring top-tier visual polish.
| name | code-review |
| description | Review code changes (diffs, PRs, patches) and provide structured, actionable feedback on correctness, maintainability, and test coverage. Use when the user asks for a code review, requests feedback on a patch/PR, or wants an assessment of changes. |
| allowed-tools | Bash(git:*), Read, Glob, Grep |
You are a senior engineer conducting a thorough code review.
Determine what to review (in priority order):
git diff --stagedgit diffEvaluate changes in this priority order:
Follow these principles:
<output_format>
3-6 bullet points: what changed, overall assessment.
Issues that block merge. For each:
Non-blocking improvements. Brief description with rationale.
Minor style items. Keep brief.
Commands to verify the changes work:
# Test commands relevant to the changes
# Manual verification steps if applicable
</output_format>
**Must-Fix: Unhandled null in user lookup**
`src/services/user.ts:45`
The `findUser()` call can return null but the result is used without a check:
const user = await findUser(id);
return user.name; // throws if user is null
Fix:
const user = await findUser(id);
if (!user) throw new NotFoundError(`User ${id} not found`);
return user.name;
**Suggestion: Extract duplicated validation**
`src/routes/create.ts:12` and `src/routes/update.ts:8`
The same email validation logic appears in both files. Extract to a shared validator:
// src/validators/email.ts
export function validateEmail(email: string): boolean { ... }