Describe the review design as current state, not as a delta

The skill read as a changelog: 'combined task review,' 'one reviewer,
one reading,' 'one dispatch,' and an example still showing diffs pasted
into prompts. A reader who never saw the two-reviewer design has no
referent for 'combined.' Prose now states the design directly, and the
flowchart/example reflect the diff-file handoff.
This commit is contained in:
Jesse Vincent
2026-06-10 08:28:28 -07:00
parent 7cf78437e2
commit 2434ef7f35
2 changed files with 16 additions and 15 deletions

View File

@@ -1,7 +1,8 @@
# Task Reviewer Prompt Template
Use this template when dispatching a task reviewer subagent. One reviewer, one
reading of the diff, two verdicts: spec compliance and code quality.
Use this template when dispatching a task reviewer subagent. The reviewer
reads the task's diff once and returns two verdicts: spec compliance and
code quality.
**Purpose:** Verify one task's implementation matches its requirements (nothing
more, nothing less) and is well-built (clean, tested, maintainable)
@@ -158,5 +159,5 @@ Subagent (general-purpose):
**Reviewer returns:** Spec Compliance verdict (✅/❌/⚠️), Strengths, Issues
(Critical/Important/Minor), Task quality verdict
A single fix dispatch can then address spec gaps and quality findings
together; re-review after fixes covers both verdicts again.
A fix dispatch can address spec gaps and quality findings together;
re-review after fixes covers both verdicts.