// Review code changes for bugs, security issues, performance problems, and style violations. Use when asked to review code, a PR, or recent changes.
Write a short implementation plan or a longer execution plan before coding. Use when starting new work, when a ticket needs clearer boundaries, when a change spans multiple files or interfaces, or when a multi-hour task needs a living plan.
Research video ideas for a topic and add them to the Airtable content pipeline.
| name | code-review |
| description | Review code changes for bugs, security issues, performance problems, and style violations. Use when asked to review code, a PR, or recent changes. |
When reviewing code, follow this process:
Run git diff (or git diff --staged for staged changes) to see what changed.
Read the modified files in full to understand the surrounding context.
Review each changed file for:
Correctness
Security
Performance
Maintainability
Format your review as:
Be direct. Don't pad with praise. Focus on things that matter.