Review

Use this workflow when reviewing a diff, pull request, branch, or local change set.

Workflow

1. Identify the review scope: diff, files, commit range, pull request, or task goal.
2. Inspect changed behavior before style or cleanup concerns.
3. Prioritize bugs, regressions, security risks, data-loss risks, and missing verification.
4. Check whether tests, docs, migrations, and release notes match the behavioral impact.
5. Look for edge cases around empty input, permissions, concurrency, rollback, and failure paths.
6. Keep findings specific, reproducible, and tied to exact files or lines when possible.
7. Avoid broad refactor suggestions unless they block correctness, safety, or maintainability.
8. If no issues are found, say so clearly and note remaining test gaps or residual risk.

When the review covers a large diff, consider delegating per-area passes to parallel subagents (for example a code-reviewer subagent per concern: correctness, security, performance, tests). Combine findings, deduplicate, and rank by severity.

Final Report