SKILL.md
Review
Use this workflow when reviewing a diff, pull request, branch, or local change set.
Workflow
- Identify the review scope: diff, files, commit range, pull request, or task goal.
- Inspect changed behavior before style or cleanup concerns.
- Prioritize bugs, regressions, security risks, data-loss risks, and missing verification.
- Check whether tests, docs, migrations, and release notes match the behavioral impact.
- Look for edge cases around empty input, permissions, concurrency, rollback, and failure paths.
- Keep findings specific, reproducible, and tied to exact files or lines when possible.
- Avoid broad refactor suggestions unless they block correctness, safety, or maintainability.
- 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
Lead with findings, ordered by severity.
For each finding, include:
- severity or priority
- file and line when available
- what can fail
- why it matters
- a concrete fix direction
Then include:
- open questions or assumptions
- verification reviewed or still missing
- brief summary of the reviewed change