health

To calculate a code health score, the skill scans your configured linting, type-checking, testing, and dead-code tools to produce a weighted 0-10 composite index. It requires access to your project's source files and installed quality tools to generate the score.

Tracking code quality trends involves storing each run's individual and composite health scores to show progress or regression over time. The skill records results from every scan, allowing you to monitor quality trends across CI builds or local checks.

Yes, the code health score tool automatically discovers configured linters, type checkers, test runners, and dead-code detectors in your repository. This toolchain discovery mechanism ensures it runs the appropriate tools to compute individual scores.

Yes, you can configure the weighting of type-checking, linting, test coverage, and dead-code scores in the health index. The skill computes individual scores for each area and combines them into a 0-10 health index using your configurable weights.

Yes, you need the relevant quality tools installed and configured in your repository to generate a code health assessment. The skill relies on accessing your project's source files and running the existing configured linters, type checkers, and test runners.

You should use a composite code quality index when you need a single, easy-to-understand metric to track technical debt or improvement over time. It is ideal for getting a quick health overview before a release or prioritizing fixes based on the combined score.