review

/adr:review — Dynamic PR review against team principles

Use when the user wants the bot to PR-review a change against the team's own conventions, not generic style rules. Requires /adr:principles to have run at least once.

Step 0 — Check principles exist

If .adr/principles.json doesn't exist in the repo, tell the user:

Your team principles haven't been discovered yet. Run /adr:principles first — it scans the repo and learns what your team's conventions are, so PR review can cite your own code.

Stop. Do not proceed.

Step 1 — Figure out what to review

If the user typed /adr:review 42, that's PR #42. Otherwise ask one short question:

What do you want me to review?

1. A PR — give me the number
2. Your staged changes (git diff --staged)
3. Your current branch vs main

Skip the question if the user already said.

Step 2 — Detect violations via the MCP server

Call adr_review with the appropriate source:

{ "pr_number": 42 }

or

{ "staged": true }

or

{ "branch": "main" }

The tool returns structured violations (each with principle_id, file, line, severity, message, suggested_fix) and the matching principles array (id, rule, rationale, examples_to_follow).

Runs in 30-90 seconds depending on diff size. Costs $0.01-$0.05 on gpt-4.1-mini.

Step 3 — If no violations: ship it

If violation_count is 0:

No principle violations in this change. Ship it.

Stop.

Step 4 — Walk through violations one at a time

For each violation in the returned list:

1. Show the user this block:

   [N/total] <SEVERITY-COLORED> file.ts:LINE
   
   Team principle: <principle.rule>
   <principle.rationale>
   
   Why this hunk fails: <violation.message>
   
   Team example to follow: <principle.examples_to_follow[0]>
   Fix: <violation.suggested_fix>
   

2. Ask one short question:

   Post / edit / skip?

3. Capture the answer. If "edit", let them rewrite the comment text. Track which violations get accepted.