Repository navigation
refactor(embedded-checks): state each pass condition as a rule - #2107
Merged
Merged
Conversation
Each check's pass condition becomes imperative bullets beside its command, with the same counts and the same refusal meaning. The report-what-a-tool-missed rule leaves; quality-gates already states it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 tasks done
This was referenced Oct 22, 2026
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
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.
Raises
core/embedded-checksfrom 83.6 to 100.0 by stating each check's pass condition as rules beside its command.Before → after, one check:
embedded-checks-extractionkeeps the extraction rulesquality-gatesReporting already states itembedded-checksChecks
No CHANGELOG entry: the rules are unchanged in meaning.
🤖 Generated with Claude Code