Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
description: Show Repowise code-health — KPIs, lowest-scoring files, refactoring targets, trends, or per-file markers. allowed-tools: Bash(repowise health:*), Read
Repowise Health
Report the code-health layer: a deterministic 1–10 score per file from markers (complexity, deep nesting, brain methods, cohesion, duplication, untested hotspots, and more). No LLM — works even in index-only mode.
Steps
- If
.repowise/doesn't exist: "This repo isn't indexed yet. Run/repowise:initfirst." Stop. - Decide the mode from
$ARGUMENTS(see below), run the command, and present a readable summary — score(s), the top marker findings, and what they mean. Don't dump the raw table verbatim.
Modes
Default (no args) — dashboard KPIs + lowest-scoring files, read from the stored analysis (no writes):
repowise health
After edits, repowise update refreshes what it reads; repowise health --recompute
analyzes the working tree in-process instead (slow on a large repo).
Handle $ARGUMENTS:
- A file or directory path →
repowise health <path>(or--file <path>for a single file) - "refactoring" / "targets" →
repowise health --refactoring-targets(ranked by impact/effort) - "trend" / "trends" →
repowise health --trend(last snapshots + declining / predicted-decline alerts) - "module " →
repowise health --module <name> - "production" / "app code" →
repowise health --scope production(tests score higher than production code, so narrowing lowers every figure without a defect having been found; the default staysall) - "code shape" / "ignore churn" →
repowise health --counts code_shape(leaves out the git-derived half: churn, co-change, ownership, prior fixes) - a coverage file (e.g.
cov.lcov,coverage.xml) →repowise coverage add <file>to ingest it (folds into health markers, and builds the per-test map when the report has contexts), thenrepowise health --recompute; a.coveragebuilds the per-test map only
Other flags: --format json for machine-readable output, -v, --verbose for
pipeline debug logs, --repo <alias> / --no-workspace in workspace mode.
Notes
- Bands are absolute, and the same five words everywhere a score appears: Excellent 8.5+, Good 7.0–8.5, Fair 5.5–7.0, Needs work 4.0–5.5, At risk below 4.0. Use those words rather than inventing your own.
- Roughly half of a score is change history, which rises as a file is worked on.
A decline is not automatically a regression — if the trend reports
history_drag, say so: the code shape did not get worse, and no edit to those files settles it. - A file that is both low-health and a churn hotspot is the highest-priority
cleanup — cross-reference with
/repowise:riskorget_risk. - If everything scores high, say so plainly rather than inventing concerns.