review
Review
Purpose
Use this as the entrypoint for local code review. Assume the implementation is wrong until it survives scrutiny. Default to finding concrete bugs, weak reasoning, unproven assumptions, and missing coverage over giving praise.
Routing Rules
- Do not read this handbook linearly.
- Pick exactly one review type first.
- Default to
robustness.mdwhen the user asks for a generic review. - If the user wants multiple review types, handle each review type separately. When subagents are available and explicitly authorized, split the types across parallel agents; otherwise review them one at a time. For formal multi-type reviews, write one review file per type.
- Follow the shared rules here plus exactly one type-specific file.
- If the user asks to review against commits, plans, files, or commands, capture
More from tstelzer/skills
skill-creator
Guide for creating or updating simple, standalone skills with a single SKILL.md file
54discovery
Use for deep design discovery and problem understanding before planning or implementation. Trigger when the user wants to think deeply, build knowledge, surface edge-cases, ask many questions, or explore the problem space without producing plans or code; save a design artifact only when durable context is requested or clearly useful.
46effect-vitest
Testing Effect programs with vitest. Use when writing tests for effect-based code.
32effect
Explains basic effect usage and terms. Use when using effect in typescript.
31review-plan-implementation
Review code changes against a plan using the plan location and implementing git commit(s).
31effect-http-server
Explains how to define http servers with effect. Use only when a top-level server is, or needs to be written in effect.
30