Repository navigation
Conversation
added 2 commits
September 3, 2026 15:36
… repo hygiene signals (v0.5.0) Scoring: every signal is now PASS / FAIL / N/A / NOT INSPECTABLE with an evidence string; category score = pass / applicable; N/A drops out of the denominator and weights renormalize. Level is set by gates (80% of a transition's requirements, cumulative) with the score table kept as a sanity check. Assessments ground on a prior report to reduce drift. New signals: doc freshness, measured CI time, branch protection via gh, dependency update automation, secret/code scanning, pinned lockfiles, release automation, gitignore hygiene, operational legibility (structured logging, health checks, tracing, alerting, runbooks), code-health scanners, instruction-file validation, agent co-authored commits, issue templates and backlog health, monorepo app scoping. Report gains Level gates, Signal evidence, and Changes since last assessment sections; validator requires Signal evidence. Roadmap marks [auto] file-only actions.
- Replace impression-based 0-100 bands in feedforward, compound engineering, context engineering, workflow artifacts, and spec-first references with PASS/FAIL profiles keyed to the category-definitions rows. - Define the denominator: exactly the rows of the two category-definitions tables; add rows for circular dependencies and doubles at seams. - Rewrite level transitions as observable requirements; move practice items to informative notes; L5 hard prerequisites stated as a cap. - NOT INSPECTABLE requirements count as not passed in gates; level marked provisional when access would change it; 80% rounds up. - Freshness is a smell (stale doc naming missing commands), not a gate; drop the 30-day threshold. - Grounding re-runs every check and reuses verdicts on identical evidence. - Branch protection scored once (CI reliability); dependency update automation moved beside pinned dependencies; dedupe structured logging. - Roadmap gap analysis starts from failing gate requirements. - CI duration from startedAt; monorepo wording; README category table.
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.
Summary
Makes the readiness assessment reproducible and auditable, and fills gaps in what it checks.
Scoring model
n/m apps.New signals
gh api, secret and code scanning in CI.gitignoreReport and roadmap
Housekeeping
Test plan
mise run buildpasses (markdownlint, manifests, cross-refs, reference integrity, 64 validator tests, gitleaks)/assess-readinesson a library and on a deployed service; confirm N/A handling and the Level gates table/assess-readinesstwice on the same repo; confirm the second run reports no changes