Development Process Fitness Review

Judge how a repository is developed, not what its code does: whether a newcomer can set it up, whether checks actually run, how changes reach the default branch, and whether decisions are visible. Much of that evidence lives in git history rather than in any file, so this review reads both.

Reference: Fundamentals of Software Development, Fundamentals of Agile Software Development, Fundamentals of Software Project Management — see also Fundamentals

Domain Knowledge

• references/rubric.md is the scoring source: severity definitions, 1-10 anchors per dimension, N/A rules, accepted evidence locations, and the overall formula. It is short; read it first.
• references/checklist.md is what to check, grouped by the seven dimensions, including pitfalls a quick existence check misses.
• scripts/git-evidence.sh gathers the history and layout numbers the rubric uses.
• references/wisdom.md is optional background generated from the source articles (about 45k tokens). Never read it whole; grep it by heading when you need the reasoning behind a practice, such as grep -n "Trunk-Based" references/wisdom.md.

Configuration

Invoke the resolver CLI to obtain effective weights and thresholds for the review target. Never load fitness-config.json directly.