review-areas
Installation
SKILL.md
Skill: Review Areas
Fan out parallel read-only subagents, each assigned a different review area, then synthesize the highest-signal findings. This surfaces issues that a single-pass review misses because each subagent goes deep on its area instead of skimming everything.
Review Areas
Pick 2–4 areas based on the nature of the change. Not every review needs all areas — match the areas to the risk profile.
| Area | When to include | Focus |
|---|---|---|
| Correctness | Always | Logic errors, type safety, race conditions, null/undefined paths, unsafe casts, wrong behavior |
| Tests | When tests exist or should exist | Run tests, check failing/missing coverage, validate assertions match intent |
| Security | Auth, input handling, data flow changes | Input validation, auth checks, injection, data exposure |
| Performance | Hot paths, data structures, async changes | Algorithm complexity, unnecessary allocations, blocking async patterns |
| Product | UI, UX, or user-facing behavior changes | UX implications, feature completeness, accessibility gaps |