Sliced Review

sliced-review

**Version 2.2.0** — see [`CHANGELOG.md`](CHANGELOG.md). Your installed version is the `version:` line in `SKILL.md`.

A Claude Code skill that reviews a whole codebase with a second model **without the budget being spent on the model wandering around the repository**.

It splits the codebase into scoped slices with explicit file lists, orders them into tiers by blast radius, and drives them one at a time with a cost ledger, an activity-aware watchdog, and an optional quota guard. Works with any headless backend — a metered subscription, a pay-as-you-go API, a local model, or a Claude subagent.

**The one idea:** the cost is in the wandering, not the thinking. A prompt that says *"review this repository"* makes the model glob, grep and read its way across everything before it reasons about anything. A prompt that says *"read exactly these twelve files, never run a repo-wide grep"* costs a fraction and returns findings.

Read [`FIELD-NOTES.md`](FIELD-NOTES.md) first — it is the measured evidence behind every rule in the skill (three parallel whole-repo lanes that burned 21% of a weekly plan for zero findings; a 20k-line codebase later reviewed for 4% of the same plan; a backend that hung silently for 19 hours).

What's in the box

Path	What it is
`SKILL.md`	The skill itself — invocation modes, then 12 steps from measuring the codebase to recording the findings
`CHANGELOG.md`	What changed in each version
`FIELD-NOTES.md`	Measured results from real runs. Why each rule exists
`references/runners.md`	How to wire a review backend: the four questions, plus worked examples
`references/templates/_context.md`	Shared context every slice prompt starts with
`references/templates/run-slice.sh`	Runs ONE slice: quota guard, idle + hard-cap watchdog, process-group kill, l