Skip to content

feat(review): read the implementer report as self-grading and keep two honesty lists - #11

Merged
z4gunn merged 1 commit into
mainfrom
feat/reviewer-trust-rules
Oct 4, 2026
Merged

z4gunn merged 1 commit into
mainfrom
feat/reviewer-trust-rules

Conversation

@z4gunn

@z4gunn z4gunn commented Oct 4, 2026 •

Copy link
Copy Markdown
Owner

Area 3 of 11: read the implementer report as self-grading, keep two honesty lists

The Code Reviewer grades the package, treats pasted output as evidence of the command it shows, never re-runs an evidenced test, grades a correctness defect by its effect on a reasonable user even when no criterion names it, and returns two lists the code-review schema now carries: declined_to_judge and cannot_verify (with the command that would answer it, which Check runs). The reviewer prompt never caps a severity or excludes an area. On a fix dispatch a developer agent verifies each finding against the code before applying it.

Source: obra/superpowers reviewer prompts.

Stacked PR: merge in order, this one after its base branch. Merge with a merge commit, as the earlier PRs were.

🤖 Generated with Claude Code

…two honesty lists

The Code Reviewer took the implementer's report at face value and had no
place to record what it set aside or could not check, so a rationale in
the report could talk a finding down and an unverifiable check was either
raised on suspicion or dropped. The reviewer now grades the package, treats
pasted output as evidence of the command it shows and nothing more, never
re-runs a test the report evidences, grades a correctness defect by its
effect on a reasonable user even when no criterion names it, and returns
two lists the code-review schema now carries: declined_to_judge for every
behavior set aside with its reason, and cannot_verify for every check the
package cannot answer with the command that would, which Check runs. The
reviewer prompt never caps a severity or excludes an area, and the reviewer
ignores such a sentence and notes it. On a fix dispatch a developer agent
verifies each finding against the code before applying it and says so with
evidence when one is wrong.

Source of the pattern: obra/superpowers requesting-code-review and
subagent-driven-development reviewer prompts, https://github.com/obra/superpowers

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Base automatically changed from feat/dispatch-files-fix-loop to main October 4, 2026 23:16
@z4gunn
z4gunn merged commit aede9a5 into main Oct 4, 2026
1 check passed
@z4gunn
z4gunn deleted the feat/reviewer-trust-rules branch October 4, 2026 23:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant