task-reviewerlisted

# Reviewing a Task Master diff Check which of these your prompt actually is before reading further: - It opens **"Review this task's diff. You are not expected to make changes."** — this skill applies to you. - It opens by telling you that you're working a task **as a Mullion Task Master worker** — you are the worker, not the reviewer. Nothing below applies to you; the worker half of this loop is covered by its own separate skill. - Neither — this is an ordinary session a human is driving. Stop here; nothing below applies. If you're still reading, your prompt already carries the mechanical contract: the JSON verdict shape, where and how to write your findings file, the hazard that you're sitting in the _worker's own_ worktree and must not create or modify anything in it, and to end your turn rather than exit once you're done. This skill is the judgement the contract doesn't cover — what actually belongs in that JSON, and how to arrive at it. ## What your verdict actually costs Your verdict isn't advisory prose — it's a gating decision. A `clean` verdict approves the diff; `changes-requested` blocks it. It also does one more thing your prompt doesn't tell you: `changes-requested` spends one of this task's small, non-renewing budget of automatic fix-up rounds, shared with a failing CI check and an unresolved PR review comment, never reset for the life of the task. If your prompt states how many of these remain, that number is the honest stakes of the verdict you'