Code Review Playbook
High-signal review discipline as a skill: fixed review order, severity labels, and language-specific traps.
by Kenji Yoshida4.5(2)918 installs
About this skill
What's inside
SKILL.mdencoding a 4-rule review discipline (think first, simplicity first, surgical comments, one-verdict endings)- Fixed review order: correctness → security → contracts → tests → simplicity → style
- Severity label system with usage rules (max 3 nits per review)
references/review-checklists.md— TypeScript, Python, Go, SQL, and concurrency traps
Use case
Inspired by the most-starred engineering-guideline skills in the community. Turns any agent into a reviewer whose comments are few, specific, and load-bearing — with a verdict at the end instead of an essay.
Versions
v2.1.0Add Go 1.22 loop semantics note; new SQL migration section7/20/2026Reviews
4.0(1)The language traps are currentDataForge Labs · 7/20/2026
The TS floating-promise and SQL migration checks catch real issues weekly.
5.0(1)Review noise dropped 70%Toolsmith Collective · 7/20/2026
The 'max 3 nits' rule and severity labels made our agent reviews something engineers actually read.