Review Skill

When to use this skill

• •before delivering final code changes
• •after implementing a planned set of steps
• •before merging or shipping

Research before reviewing

Before applying the checklist, search for context in parallel:

• •search_web for latest best practices and known issues in the libraries/frameworks used (scope to stack.md versions).
• •search_web for security advisories or deprecation notices relevant to the APIs in use.
• •Read all changed files in parallel to build full context.

Severity levels

• •Blocker: wrong behavior, security issue, data loss risk, broken tests/build
• •Major: likely bug, missing edge cases, poor reliability
• •Minor: style, clarity, small maintainability issues
• •Nit: optional polish

Checklist

1. •Correctness vs requirements
2. •Edge cases & error handling
3. •Tests (adequate coverage, meaningful assertions)
4. •Security (secrets, auth, injection, unsafe defaults)
5. •Performance (obvious hotspots, N+1, unnecessary work)
6. •Readability & maintainability
7. •Docs / comments updated if needed
8. •Patterns match latest framework best practices (from research)

Output format

• •Blockers
• •Majors
• •Minors
• •Nits
• •Overall summary + next actions