review-pr

PR Review Skill

Reviews a branch against main, checks plan/spec/style compliance, rates the PR, and produces a fix document for the author.

Trigger

/review-pr [branch-name]

If no branch is given, compare the current branch against main.

Command-line Tools

• use fd instead of find
• use rg instead of grep

Process

Step 1: Load Context

Read these three things — nothing else:

1. Project memory (always):

   Derive the memory directory from the current working directory:

   MEMORY_DIR="$HOME/.claude/projects/$(pwd | sd '/' '-')/memory"
   

   • Read $MEMORY_DIR/MEMORY.md (the index). If it exists, read every memory file linked in the index.
   • If MEMORY.md does not exist but the directory does, read all *.md files in the directory directly.
   • If the directory is missing or empty, note that no project memory is available and proceed with the diff alone.

2. Phase plan (always):

   Locate the authoritative spec for this branch. Try in order:

   • Parse the branch name for a phase identifier (e.g., phase-4-density-mixing → look for 4). Search: fd -e md -e toml . plans/ | rg -i 'phase.?{N}'
   • If a plans/ directory exists and contains exactly one plan file, use it.
   • If the notes/plan-reviews/ directory exists, check for a decisions.md file that names the plan path.
   • If no plan is found: note "No phase plan found — scope gating disabled; all issues treated as [Correctness]." and proceed without a spec.

   When found, read the full plan. This is the authoritative scope spec — issues must be justified against it.

3. Branch status snapshot (if it exists):

   notes/pr-reviews/{branch}/status.md
   

   The snapshot contains the post-fix diff, changed-file list, build/test results, and outstanding issues — it is the complete picture of the branch state.

If the snapshot exists: stop reading here. Do not read any source files, run any git commands, or call any LSP tools. Proceed directly to Step 2 with the plan and snapshot in context.