---

name: code-review description: 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.

Code Review

Interactive guided tour through code changes.

Quick Start

Copy# 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:

Copy| 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:

CopyEntry 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:

Copy**PR Summary:**
- Main feature added
- Supporting changes
- Dependencies/config updates

Ready to merge, or any concerns?

Tour Stop Format

Copy## [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

External PR URLs

When given a GitHub URL like https://github.com/owner/repo/pull/123:

1. Parse owner, repo, and PR number from URL
2. Use -R owner/repo flag for gh commands:

Copygh pr view 123 -R owner/repo --json title,body,author,state,additions,deletions,files,baseRefName,headRefName
gh pr diff 123 -R owner/repo

1. Follow the standard review protocol above