Pull Request Review
Context
- •Branch: !
git branch --show-current - •PR metadata:
!gh pr list --head "$(git branch --show-current)" --json number,title,body --limit 1
If a PR number is provided as an argument ($ARGUMENTS), use that instead.
Steps
- •Retrieve the PR diff with
gh pr diff <number>. - •Retrieve review comments with
gh api '/repos/{owner}/{repo}/pulls/<number>/comments'. - •Read the changed files to understand context beyond the diff.
Review Checklist
- •Logic errors, edge cases, off-by-one errors
- •Security concerns (injection, auth, data exposure)
- •Error handling adequacy
- •Naming clarity and code readability
- •Dead code and orphaned references introduced by the changes
- •Deleted files may leave behind unused imports, type definitions, routes, or assets. Trace references transitively until no more orphans are found.
- •Test coverage for changed behavior
- •Consistency with existing codebase patterns
Project-specific Checklist
!cat .claude/skills/review-checklist.local/SKILL.md 2>/dev/null
Output
Save the review to .ignore/reviews/<number>_<branch>/<YYYYMMDD>_<seq>.md.
- •Replace
/in branch names with_. - •If a file with the same name exists, increment
<seq>(2-digit, zero-padded). - •Example:
.ignore/reviews/123_feature_add-auth/20240401_00.md