Software Testing Fitness Review

Analyze the codebase (or specified files/modules) for software testing fitness. Evaluate test quality, coverage strategy, pyramid balance, and testing infrastructure using evidence from test files, the code they test, CI configuration, and production support tooling.

Reference: Fundamentals of Software Testing — see also Fundamentals of Software Quality Assurance and Fundamentals

Domain Knowledge

• references/rubric.md is the scoring source: severity table, 1-10 anchors per dimension, N/A rules, how to cite an absence, and the overall-score formula. Read it first; it is short. Scores are only repeatable if every run uses the same anchors.
• references/checklist.md is what to check during the workflow steps. Its section 6 (QA Process) has no dimension of its own: its feedback-loop checks score under CI Integration and its regression and definition-of-done checks under Coverage Strategy.
• references/wisdom.md is optional background, generated from the two Fundamentals articles. It has no rubrics. Grep it by heading for a specific question (for example grep -n '^### ' references/wisdom.md); never read it whole.

Configuration

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

python3 "${CLAUDE_SKILL_DIR}/../../scripts/fitness-config.py" show --path <target>