code-review

# Code Review Use this skill to review local changes or an existing GitHub pull request for correctness, regressions, maintainability, security, and missing tests. ## Review Order 1. Establish scope with `git status --short`, `git diff --stat`, and `git diff --name-only`. 2. Read the changed files, not just the diff, before judging behavior. 3. Run targeted validation when it exists: tests, typecheck, lint, build, or repo-specific checks. 4. Present findings ordered by severity, then open questions, then a brief summary. ## Primary Workflows ### Local Branch Review Use local git state when the change is in the current checkout: ```bash git status --short git diff --stat git diff --name-only git diff --staged git diff <base-branch>...HEAD git log --oneline <base-branch>..HEAD ``` Replace `<base-branch>` with the repository's actual review base branch. ### GitHub PR Review Use `gh` when the review target is an open pull request: ```bash gh pr view 123 gh pr diff 123 gh pr checkout 123 gh pr view 123 --comments ``` After checking out the PR branch, review it the same way as a local branch and run the relevant repo checks before leaving comments. ## What to Look For Prioritize issues that change behavior or raise delivery risk: - incorrect logic or broken edge cases - state, data, or migration regressions - auth, permission, or secret-handling mistakes - missing validation, retries, or error handling - flaky or incomplete tests - risky coupling, hidden sid...