Review

Input

• A PR, branch, commit range, diff, file list, feature scope, or review category.
• Use explicit input first; otherwise infer from context, recent edits, selected files, or branch.
• Safest default: review current changes for correctness, regressions, tests, security, dependencies, product mismatch, and operational risk.

Workflow

1. Identify input. Determine whether the review target is a PR, branch, commit range, diff, files, or current worktree.
2. Read context. Check relevant specs, issues, AGENTS.md, docs, tests, and config that define expected behavior or standards.
3. Inspect changes. Review for correctness, regressions, missing tests, security risks, dependency risks, error handling gaps, operational risk, and product/spec mismatch.
4. Prioritize findings. Report actionable issues first, ordered by severity, with file and line references when possible.
5. Separate uncertainty. List open questions, assumptions, and residual risks after findings.
6. Report only. Do not edit code unless the user explicitly asks for fixes.

Output