/code-review

/code-review

Input: $ARGUMENTS

Mode Selection

If $ARGUMENTS contains a PR number, PR URL, or --pr → PR Review Mode.

Otherwise → Local Review Mode.

---

Local Review Mode

Phase 1 — GATHER

git diff --name-only HEAD

If no changed files, stop: "Nothing to review."

Read CLAUDE.md (if present) for project conventions. Read each changed file in full.

Phase 2 — REVIEW

Spawn the code-reviewer agent with:

• Full file contents of each changed file
• CLAUDE.md contents (if present)
• Recent context: git log --oneline -5

Phase 3 — VALIDATE

Detect the project stack and run the appropriate build + test commands:

# .NET
dotnet build --no-restore -q && dotnet test

# Node / TypeScript
npm run build && npm test

# Python
python -m pytest

# Or use task runner if present (Makefile, Taskfile, package.json scripts)

Report pass/fail for build and tests separately.

Phase 4 — REPORT

Present the agent's findings plus build/test results:

---
## Review Summary

| Severity | Count |
|----------|-------|
| CRITICAL | 0     |
| HIGH     | 1     |
| MEDIUM   | 2     |
| LOW      | 0     |

Build: PASS / FAIL
Tests: PASS / FAIL

Verdict: APPROVE | WARNING | BLOCK

Decision rules:

• APPROVE — no CRITICAL/HIGH, build + tests pass
• WARNING — HIGH issues only (can merge with caution)
• BLOCK — any CRITICAL issue or build failure

---

PR Review Mode

Phase 1 — FETCH

Input	Action
Number (42)	Use as PR number
URL (github.com/.../pull/42)	Extract PR number

gh pr view <NUMBER> --json number,title,body,author,baseRefName,headRefName,changedFiles,additions,deletions
gh pr diff <NUMBER>

Phase 2 — CONTEXT

1. Read CLAUDE.md for project constraints
2. Parse PR description for goals and linked issues
3. Read each changed file in full

Phase 3 — REVIEW

Spawn the code-reviewer agent with full file contents and CLAUDE.md.

Additionally check:

• Migration safety — new NOT NULL columns must have defaults or be nullable
• No missing migration — if entity/schema changed, check for matching migration file
• Breaking changes — public API changes that could break consumers

Phase 4 — VALIDATE

Run build + test commands as in Local Review Mode.

Phase 5 — PUBLISH

# Approve
gh pr review <NUMBER> --approve --body "<summary>"

# Request changes
gh pr review <NUMBER> --request-changes --body "<summary with required fixes>"

# Comment only (draft PR)
gh pr review <NUMBER> --comment --body "<summary>"

For inline comments:

gh api "repos/{owner}/{repo}/pulls/<NUMBER>/comments" \
  -f body="<comment>" \
  -f path="<file>" \
  -F line=<line-number> \
  -f side="RIGHT" \
  -f commit_id="$(gh pr view <NUMBER> --json headRefOid --jq .headRefOid)"

Phase 6 — OUTPUT

PR #<NUMBER>: <TITLE>
Decision: APPROVE | REQUEST CHANGES | BLOCK

Issues: <critical> critical, <high> high, <medium> medium, <low> low
Build: PASS / FAIL
Tests: PASS / FAIL

Next steps: <contextual suggestions>

Related Agent

Invokes the code-reviewer agent — see .claude/agents/code-reviewer.md.