reviewlisted

# review After an hour at the pass you cannot taste your own seasoning. The chef sends a plate to a cook who did not make it, because the person who built the dish has gone nose-blind to it. This skill is that second palate for code: dispatching a fresh reviewer that sees the work product, not the hour of reasoning that produced it. It is the independent pass that [pass](../pass/SKILL.md) calls for and the producer of the feedback that [sendback](../sendback/SKILL.md) acts on. **Core principle:** the reviewer gets the work and the requirements, never your session history. A reviewer fed your reasoning reviews your reasoning; a reviewer fed the diff reviews the code. Crafted context keeps it honest and keeps your own context free for the work. ## When to request a review - After each task in a plan or [stations](../stations/SKILL.md) fan-out, before the next one compounds on it. - After a major feature, before merge to a shared branch. - On any change to a repo you do not own. - Optionally when stuck, for a fresh angle. A one-line, obviously-safe change (a dependency bump, a typo) does not need this; the [pass](../pass/SKILL.md) self-review covers it. ## How to run it **1. Pin the range.** ```bash BASE_SHA=$(git rev-parse HEAD~1) # or origin/main, or the task's starting commit HEAD_SHA=$(git rev-parse HEAD) ``` **2. Dispatch a reviewer subagent** with a complete, self-contained ticket. It inherits nothing, so the prompt is everything it knows: ``` You are reviewing