code-review
Reviews code changes with brief annotations. Use when user says "review code", "review changes", "what changed", "review pull request", "review PR", "review the pr", "review this pr", "review [name]'s pr", "review new pr", "review latest pr", "let's review", "review https://github.com/.../pull/123", or runs /code-review.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Code Review
Interactive guided tour through code changes.
Quick Start
# For PRs: get PR info and diff
gh pr list
gh pr view <number>
gh pr diff <number>
# For local changes
git diff HEAD --stat
Review Protocol
1. Overview (2-3 sentences max)
What the PR/changes accomplish at high level.
2. Offer Branch Switch
For PRs, offer to checkout the branch so user can explore in IDE alongside.
3. Tour Map
Show grouped file list so user sees full scope:
| Group | Files |
| ------------ | ------------------------ |
| Core feature | `main.py`, `helper.py` |
| Utilities | `utils.py`, `config.py` |
| Docs | `README.md`, `CHANGELOG` |
4. File-by-File Tour
Walk through each changed file:
- Brief description of what changed
- At complex points: offer to trace execution flow
- Batch small/related files into single stops (e.g., utils + related refactors)
- End each stop clearly: "Questions, or next file?"
5. Flow Tracing (on-demand)
When user wants to understand a specific feature deeper, trace the execution path:
Entry point (e.g., handler receives message)
↓
Layer 2 (calls helper function)
↓
Layer 3 (calls API/database)
↓
Back up the stack with result
This shows how pieces connect across files.
6. Wrap-up
Quick summary of key changes when tour completes:
**PR Summary:**
- Main feature added
- Supporting changes
- Dependencies/config updates
Ready to merge, or any concerns?
Tour Stop Format
## [filename.py](path/to/file.py) (+X/-Y)
**What changed:**
• Change 1
• Change 2
**Key point:** [explanation of important logic]
→ Want to trace how [feature X] flows through the code?
Questions, or next file?
Guidelines
Include:
- Functional changes (new logic, modified behavior)
- Security-sensitive code
- Breaking changes
- New dependencies
Skip:
- Import reordering
- Formatting-only
- Comment typos
- Lock files, generated code
Scope Options
| Scope | Command |
|---|---|
| PR | gh pr diff <number> |
| Uncommitted | git diff HEAD |
| Staged only | git diff --cached |
| vs main | git diff main...HEAD |
| Last N commits | git diff HEAD~N..HEAD |
External PR URLs
When given a GitHub URL like https://github.com/owner/repo/pull/123:
- Parse owner, repo, and PR number from URL
- Use
-R owner/repoflag for gh commands:
gh pr view 123 -R owner/repo --json title,body,author,state,additions,deletions,files,baseRefName,headRefName
gh pr diff 123 -R owner/repo
- Follow the standard review protocol above
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!