CI/CD & release
Whether the path from commit to release is automated and honest: CI exists and no job swallows failures, releases and changelogs are derived mechanically from Conventional Commits, and the same verify gate runs locally before a commit ever reaches CI.
5.0 / 510 of 10 weighted points earned — snapshot of 2026-08-04
ci-presentweight 1 ptearned 1 / 1
Measures: a CI workflow exists
Why this weight: Table stakes — everything else in this dimension presumes it, so bare presence earns the minimum.
no-continue-on-errorweight 2 ptsearned 2 / 2
Measures: no CI job silently swallows failures
Why this weight: A swallowed failure rots the signal of every other check CI runs — green must actually mean green.
release-automationweight 2 ptsearned 2 / 2
Measures: release-please configured
Why this weight: Removes human error from versioning and changelogs, making releases reproducible decisions instead of rituals.
conventional-commitsweight 2 ptsearned 2 / 2
Measures: commitlint + commit-msg hook enforce Conventional Commits
Why this weight: The machine-readable history that release automation depends on; enforced at commit time, it keeps the changelog derivable rather than curated.
precommit-gateweight 2 ptsearned 2 / 2
Measures: a pre-commit hook runs the verify gate
Why this weight: Catches failures before they ever reach CI, and — because it is a git hook — applies to any agent or human, per the project’s agnosticity principle.
knip-in-ciweight 1 ptearned 1 / 1
Measures: dead-code analysis runs in CI
Why this weight: Valuable hygiene, but a narrower concern than gates and release automation — hence the smallest weight.