Skip to content

refactor(quality-gates): shorter lead-ins, pass conditions as rules - #2116

Open
braboj wants to merge 1 commit into
mainfrom
refactor/quality-gates-score
Open

braboj wants to merge 1 commit into
mainfrom
refactor/quality-gates-score

Conversation

@braboj

@braboj braboj commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

Raises core/quality-gates from 92.5 to 97.9. Its weak criterion was paragraph share: lead-ins and two pass conditions were 22% of its prose.

Section Change
Intro, Paired checks, Check subject, Gate scope, Scope coverage, Environment independence, Test edits Each lead-in → one sentence, same claim
Scope coverage The devsecops example note dropped; the rule above it covers it
Site-local suppressions Pass condition → two rules: the counts; what zero files scanned means
Test edits Pass condition and the three paragraphs after it → five rules: the MUST count, --base/--tests, not applicable, line counts as a reading, a zero range
  • The 80-column example keeps its "Pass condition:" paragraph: it illustrates the form the rule above it names
  • Fences unchanged, so each conformance disposition still finds its block
  • MUST lines (4) and SHOULD/MAY count (3) unchanged
  • Part of Raise every template's quality score to at least 95 #2106

Checks

  • Smoke 35/35; conformance 12 passed, 0 failed, 1 not applicable; readings read
  • Fork sync, redundancy audit, score ratchet, markdownlint, pre-commit hooks

No CHANGELOG entry: the rules are unchanged in meaning.

🤖 Generated with Claude Code

Lead-in paragraphs shrink to one sentence each; the suppression and
test-edit pass conditions become rules beside their commands with the
same counts and refusals. Every MUST, SHOULD and MAY stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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