Zen Review

Every skill named here is required. When a step names one (/name), invoke it with the Skill tool at that step and follow it in full. Working from memory of a skill is not following it.

A system's description is its code plus everything a consumer must hold in their head to use it. Correctness makes the description true. Shape makes it smaller. Review, fix, and verify autonomously. In report-only or review-only mode, make no edits.

1. Scope

request -> target: the files under review, the base, the spec

List the files under review: git diff <base> (uncommitted: HEAD; branch: merge base; PR: fetch it) plus untracked files, which git diff never shows; or the named paths when there is no diff. Note the spec, ticket, or plan if one is named. Name unrelated dirty files and leave them.

2. Find

finders -> raw findings -> deduped findings = working set

This run looks at the target as it stands now. Carry nothing from earlier runs; the repo's own history stays readable. Rerunning after fixes is the normal loop. Use the same target and the same finder prompts each run: a prompt shaped by the last run's findings steers finders, and an unchanged one makes a shrinking list a real signal. Within a run, the fix diff goes to Verify, not back here.