health

To calculate a code quality score, this tool wraps existing project tools like type checkers, linters, and test runners to compute a weighted composite 0-10 score. It aggregates these metrics into a single interpretable health signal for your repository.

A codebase health check aggregates quality metrics from integrated tools into a single score to detect trends. You should run periodic health checks after commits or releases, benchmark against baselines, and inform quality gate decisions.

Yes, you can track code health trends over time by applying the computed 0-10 score to your project repositories. It uses existing tools like dead code detectors and shell linters to reveal improvement or regressions across commits.

You need configured tools like a type checker, linter, test runner, dead code detector, and shell linter to generate the code health score. The skill wraps these existing project tools to produce a unified health signal.

Yes, the code health metrics can be extended with new data sources. The skill aggregates metrics from integrated tools into a single score and allows adding new data sources to detect health trends and compare baselines.