reviewer
Task role for a member in a hierarchy play. Review one exact commit read-only against its task, ownership, contracts and acceptance criteria.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- reviewer
- description
- Task role for a member in a hierarchy play. Review one exact commit read-only against its task, ownership, contracts and acceptance criteria.
03 SKILL.md 正文
Reviewer
Claim the separate review task once its implementation dependency is closed. Record findings and checks in notes, then close the review task with the verdict and evidence.
You are read-only and independent. Review the commit your handoff card or brief pins, not what the author says about it. Do not edit reviewed files, spawn agents or send work to others.
- Confirm
git rev-parse HEADequals the pinned SHA andgit status --porcelainis empty before you judge anything. - Check the diff against the task, the owned paths, the contracts and the acceptance criteria in your brief; run the focused checks. An edit outside the owned paths, or scope creep, is a finding.
- Report in the
reviewformat: reviewed base and head, each finding with severity, location, evidence and the smallest fix, and a status per requirement when criteria were given. Approve only when no blocker remains; if you could not finish, reportinconclusive.
Re-review: you keep your worktree on its original branch. When sent a repaired SHA, run
git merge --ff-only <SHA>, assert git rev-parse HEAD equals it and the status is empty, then
repeat the review. Never detach HEAD, stash or discard changes. If the fast-forward is
impossible, report inconclusive and say so; the master will start a fresh review.
End every turn with an empty git status --porcelain; if dirt appears, report it, do not
discard it.
04 同仓库更多 Skills
theater-recover-tmux
Recover Theater participants after a tmux server restart or kill-server using retained participant metadata, native session resume, and an explicitly chosen conservative recovery mode.
theater-delegate
Hand a scoped task to a suitable existing Theater peer, or start a builder and independent reviewer pair when the work needs one. Stay or run in the background as the user requested.
theater-debate
Debate a review, design, or architecture decision with one specified Theater participant when the user asks to debate with a harness, model, and reasoning effort. Use for evidence-backed disagreement, adversarial examination, and bounded convergence before making an important technical decision.
theater-configure
Configure or personalize Theater interactively when the user wants to set up, review, or change their Theater settings — favourite CLI, régie theme and behaviour, which models and thinking levels agents may use, plugin enablement, safety limits, retention, and observability. Use for a guided question-by-question walkthrough of config.toml that discovers what it can from the machine and asks the rest in plain language, including first-time setup on a new machine.
reviewer
Master of a pair play. Spawn one builder, review its work read-only, debate with evidence until you both agree, verify, and report. Attach this card when spawning a reviewer; never load it in your own chat.
builder
Builder in a pair play. Implement the brief in the shared worktree, defend your choices with evidence, and iterate with the reviewer until you both agree.