Use when the user asks about code health, code quality, complexity, technical debt, which files are risky or hard to maintain, what to refactor next, untested hotspots, or coverage gaps in a Repowise-indexed codebase (.repowise/ directory exists). Also use to get a before/after health read when planning or finishing a refactor.
$npx -y skills add repowise-dev/repowise --skill code-healthInstalls into the current project.
Run `npx skills use "https://github.com/repowise-dev/repowise" --skill "repowise-dev/repowise/code-health"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/repowise-dev/repowise" that are relevant to the current task. Run `npx skills add "https://github.com/repowise-dev/repowise"` and select the relevant skills, then follow their instructions.