campfire: Skill for Claude Code

Codebase review sweeps

A sweep has two halves. The review finds and verifies issues, fixes the simple ones on the spot, one commit each, and writes a plan for each complex one. The execution lands those plans, in a later turn, and only starts when the user says so — never roll from the review into it.

When to run: at milestones only — after a planned program lands, before a major release, or when the owner asks; never after every batch of commits. Between them, the checks in the loop (the edit hook, the pre-commit hook) keep quality.

0. Before anything

• Read the memory notes of earlier reviews (MEMORY.md lists them). Do not re-review an area the last sweep found solid, re-raise a finding that was rejected or disproven, or re-ask a decision the user already took — the notes record all three.
• Look at the plans folder (see the last section). If plans from an earlier sweep are still there, ask whether to keep them, fold them in or clear them before writing new ones. Never delete untracked plans on your own.
• Note git rev-parse --short HEAD and the branch; every document names that commit, and it is the start of the range the review's own fixes land in. If the working tree has uncommitted work, say so: fixes stage only their own paths, and a finding in a file with pending changes is planned rather than fixed.
• Agree on the angle and the budget if the request leaves them open. The yield comes from a new angle (a platform barely run, bad network, low-end devices, scale, stress/monkey tapping, a store's rules), not from looking harder at the same code. If the user caps tokens or time ("an hour is enough"), size the fan-out to it: fewer reviewers, one live run at most.
• Pick each agent's model for its job, without being asked. Judgement — area reviewers, plan writers, challengers, lane agents — runs on the most capable model. Matching text against the code — the docs check, a regression read of docs-only commits, applying already-written doc fixes, mechanical moves — runs on a cheaper one (sonnet; haiku for plain grep-and-compare). Prefer doing a small mechanical job yourself over spawning anything.