Repository navigation
Prefer a repository check over another always-on prose rule - #5
Merged
Merged
Conversation
A review of agent instructions, or of a change that exists only to stop an agent repeating a mistake, should prefer a test, a lint, or removing the need for the instruction before adding another always-on prose rule. Co-authored-by: Dennis Geldmacher <geldmacher.dennis@outlook.de>
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.
Reviews of agent instructions and changes intended to prevent repeated agent mistakes now prefer repository checks or structural changes that make additional instructions unnecessary. Concise guidance remains appropriate when the agent still needs the requirement, including when a check also enforces it.
The policy lives in the existing agent-document design reference. Context optimization loads it for instruction reviews; code reviews reach it through a conditional link for changes intended to prevent repeated mistakes. The usage guide adds a matching example. Reviews recommend changes and retain the existing authorization boundary for implementation.
Validation:
git diff --checkandnpm run release-checkpassed locally, including all 114 tests with no failures or skips.