code-review-pipeline

<quick_start>

1. •Run /code-review-pipeline after making code changes
2. •Reviewers dispatch automatically based on file types
3. •Critical/high findings are fixed inline; medium/low reported as suggestions </quick_start>

<when_to_use> Use when:

• •You've implemented a feature and want to catch issues before committing
• •Before finalizing a branch or PR
• •After a significant refactor
• •User asks for a code review

Don't use when:

• •Only config/docs changed (no code to review)
• •Single-line trivial fix </when_to_use>

1. •The implementation reviewer is ALWAYS dispatched
2. •Deduplicate categories into a set of reviewers to dispatch </phase>

For EACH reviewer, construct a prompt that includes:

1. •The full git diff
2. •The list of files relevant to that reviewer
3. •Instructions to return JSON in the standard output format

Dispatch map:

Launch all applicable reviewers as parallel Task calls in a single message. Use model: sonnet for each.

Prompt template for each reviewer:

Review the following code changes. Return your findings as JSON.

## Changed files
{file_list}

## Diff
{diff_content}

1. •Compile missing tests list from all reviewers </phase>

Critical and High findings

For each critical/high finding:

1. •Read the file at the specified line
2. •Apply the recommendation to fix the issue
3. •Report what was fixed

Medium and Low findings

Report as suggestions in a summary table:

## Review Summary

**Reviewers:** implementation, test, ui
**Files reviewed:** 5
**Findings:** 2 critical, 1 high, 3 medium, 1 low

### Fixed (Critical/High)
- [critical] src/auth.ts:42 — SQL injection via string interpolation → switched to parameterized query
- [high] src/api.ts:15 — Uncaught promise rejection → added try/catch

### Suggestions (Medium/Low)
| Severity | File | Line | Issue | Recommendation |
|---|---|---|---|---|
| medium | src/utils.ts | 23 | Potential null dereference | Add null check before access |
| low | src/config.ts | 8 | Magic number | Extract to named constant |

### Missing Tests
- Test error path when fetchUser throws in src/auth.ts:42
- Test empty array input in src/utils.ts:23

If no findings above confidence threshold: report "Review complete — no issues found." </phase>

<error_handling>