dev-review

Topics in the source

• dev-review
• When to Use
• Checklist
• Rationalizations
• Red Flags
• Verification

Paths: the bin/ tools and the library/ folder live in /.agents/dev-kit/; run tools by that path. Task: no DEVKITTASK set? Run /.agents/dev-kit/bin/ledger start first (it prints your id) and prefix dev-kit commands with DEVKITTASK= . below is .devkit/tasks/ at the repo root; never write run files anywhere else. Also read .devkit/memory.md if it exists. Open the host todo list (todowrite, TodoWrite or TaskCreate, whichever exists; else a checklist in /state.md) with this checklist verbatim, and tick items as steps finish. A skipped step stays listed with a reason. Run bin/ledger after every step (phase=review). Before merging or committing a non-trivial diff, after a ship worker returns, or when reviewing a branch or PR. Tiny diff: self-review with the same axes and ledger that you did. You own: findings on two axes (Standards and Spec) with a recorded disposition for each. Reads: always library/principles (step 0), library/simplify, library/doubt, library/state, library/deep/blast-radius. If the diff touches security: library/security. If it touches performance: library/performance. If it touches a runtime path: library/observability. [ ] 0. Skim library/principles (about 700 tokens

This is an excerpt. Refer to the complete source and its current requirements.