Repository navigation
refactor(frontend-quality): one instruction per rule - #2118
Merged
Merged
Conversation
The pattern catalogue's bold labels and the linting, CSS and analytics statements become instructions; the "where appropriate" hedge names the case each pattern fits. Every MUST, MUST NOT and SHOULD stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # tests/baselines/template-quality.txt
2 tasks
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
1 participant
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
frontend/qualityfrom 93.5 to 98.3: its rules were noun phrases and statements, and one carried a hedge.Checks
No CHANGELOG entry: the rules are unchanged in meaning.
🤖 Generated with Claude Code