Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From repowise
Assesses code health, technical debt, and refactoring priorities in a Repowise-indexed codebase. Reports file-level scores (1-10) based on complexity, cohesion, churn, and coverage biomarkers.
npx claudepluginhub repowise-dev/repowise --plugin repowiseHow this skill is triggered — by the user, by Claude, or both
Slash command
/repowise:code-healthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Repowise scores **every file 1–10** from deterministic biomarkers — McCabe
Scans codebase health by identifying hotspots, risky files, and coupling patterns. Prescribes prioritized refactoring actions with ROI-based guidance. Invoke via /Vitals or rely on auto-activation when discussing code quality.
Analyzes codebase complexity, dependencies, dead code, tech debt, and git hotspots. Produces a health score and rescue plan for legacy projects or external repo evaluation.
Explains Code Health fundamentals, score interpretation, and why it matters for maintainability and delivery speed.
Share bugs, ideas, or general feedback.
Repowise scores every file 1–10 from deterministic biomarkers — McCabe complexity, deep nesting, brain methods, class cohesion (LCOM4), god classes, clone detection, untested hotspots, function-level churn, ownership dispersion, and more. Zero LLM calls; pure local analysis. The weights are calibrated against a real defect corpus, so a low score means more likely to harbour bugs, not just bigger.
get_health() (no targets): repo-level KPIs plus the
lowest-scoring files. Start here for "how healthy is this codebase?" or "what
should we clean up?".get_health(targets=["src/x.py", "src/y.py"]): per-file score
and the specific biomarker findings driving it. Use before/after a refactor,
or to explain why a file is flagged.include flagsget_health(targets=[...], include=[...]):
"biomarkers" — always return the findings list (what's wrong, where)."refactoring" — deterministic, ranked refactoring suggestions (by impact/effort)."coverage" — surface coverage data when it's been ingested."trend" — recent health snapshots + declining / predicted-decline signal.get_health(targets=[worst files], include=["refactoring"]) and present the
ranked suggestions, not just the scores.get_risk(targets=[...]); a file
that is both low-health and a churn hotspot deserves the most care.repowise health --coverage cov.lcov
(LCOV / Cobertura / Clover).repowise health — KPIs + lowest-scoring filesrepowise health --refactoring-targets — ranked by impact / effortrepowise health --trend — snapshots + declining alertsrepowise health --coverage <file> — ingest coverage, light up untested-hotspotIf get_health reports no repository, suggest /repowise:init. Code health is
computed even in index-only mode (no LLM needed), so it should be available
whenever the repo is indexed.