Full Project Fitness Review

Run the ten domain review skills in parallel and combine their results into one weighted fitness report. This skill does not score code itself; it decides scope, reads weights from the resolver, aggregates, and shows its arithmetic so the overall can be checked by hand.

Configuration

Always invoke the resolver CLI to read effective weights and thresholds. Never load fitness-config.json directly. The CLI walks up from the review target to find module overrides and merges them with the root config per ADR-001 / ADR-002 / ADR-005.

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

${CLAUDE_SKILL_DIR} is this skill's directory; the resolver ships two levels up in the plugin's scripts/. If your agent does not expand the variable, substitute the directory containing this SKILL.md.

Where <target> follows the scope chosen in Step 1:

• User-given path: that file or directory.
• Pending changes: each changed file. Override files are often gitignored, so a module override can govern a changed file without showing up in git status; resolving per file is the only way to catch it. Group the files by the Config: line they resolve to.
• Whole project: the repository root (per ADR-005, only the root config applies at root scope).