health

You can track code health trends by computing the weighted 0-10 health score over time, which visualizes improvements or regressions across your codebase. The dashboard-like summary stores historical health-score data for routine quality reviews.

The best way to consolidate dead code detection and shell linting into a health check is running a full suite scan that aggregates results into a weighted 0-10 score. This approach supports routine checks and refactor planning for any codebase size.

Yes, the code health dashboard works with codebases of any size to assess overall quality and track trends. It requires the underlying tools, such as the type checker and linter, to be available in the environment to produce the summary.

You need the underlying tools, including the type checker, linter, test runner, dead code detector, and shell linter, to be available before running a code health check. The Skill requires these external dependencies to execute and generate the weighted score.

Your weighted health score changes because the tool tracks trends over time by re-running type checkers, linters, and tests, reflecting current code quality. This historical trend analysis visualizes recent improvements or regressions in the codebase.