Add test-change discipline to Designer, Coder, and Reviewer prompts - #10
Merged
Merged
Conversation
Designer now explicitly lists which existing tests need to change as part of its design output. Coder is prohibited from modifying existing tests unless the task description names them; undocumented test changes require a review item. Reviewer rejects any existing-test modification not explicitly listed in the task — new tests are always permitted.
wparad
added a commit
that referenced
this pull request
Jul 25, 2026
…-fznmgy Add test-change discipline to Designer, Coder, and Reviewer prompts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
EXISTING TESTSsection prohibits modifying any existing test unless the task description explicitly names it and describes the required change. Undocumented test changes must be surfaced viagitzi_create_review_item. Adding new tests remains unrestricted.Together these three rules close the loop that caused the CI breakage in the previous PR — the Coder silently updated a test that the task never mentioned, and neither the design nor the review caught it.
Generated by Claude Code