Skip to content

refactor(git): state each pass condition as a rule - #2110

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

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

Conversation

@braboj

@braboj braboj commented Oct 21, 2026 •

Copy link
Copy Markdown
Collaborator

Raises core/git from 89.4 to 98.6 by stating each pass condition as rules beside its command, as #2107 does for embedded-checks.

Section Change
CI evidence Pass condition → require registered > 0, not passing = 0, zero exit; never merge on a non-zero exit
Regenerated artifacts Pass condition → require no diff and zero status; a non-idempotent regenerator is defective
Regenerated artifacts Bidirectional-artifact rule split: never regenerate from the pipeline; refresh through the person's step
Regenerated artifacts Empty-diff note → a rule naming git checkout -- <file>
Off-limits paths Pass condition → four rules: counts, --path and --base, escalation not failure, run after committing
Off-limits paths Executable-content rule split from "prose is ordinary work"

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

The three pass-condition paragraphs and the empty-diff note become
rules beside their commands, with the same counts and refusals. Long
compound rules split in two. Every MUST and MUST NOT 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