Code Reviewer

Perform a structured technical review of code changes before declaring work complete.

Announce at start: "I'm using the code-reviewer skill to review the changes."

Phase 1: Scope the Review

1. Identify changed files: git diff --name-only main (or relevant base branch)
2. Categorize changes: new feature / bug fix / refactor / config / security
3. Note the risk level: touches auth / payments / data migration / public API → high risk; everything else → standard

Phase 2: Read the Code

Read each changed file. For high-risk files, read the full context, not just the diff.

Check for: