health

You can aggregate code quality checks into a single score by using a skill that automatically detects and executes available type checkers, linters, and test runners, then computes a weighted composite 0-10 health metric. This eliminates manual tallying of disparate tool outputs.

A composite code health score is a weighted 0-10 metric calculated from the outputs of various code quality tools. It works by automatically detecting and running configured type checkers, linters, test runners, and dead code detectors, then aggregating their results into one actionable dashboard.

Yes, you can track codebase health trends over time without manual tool configuration by using automated tool detection. The system identifies available linters and test runners, computes a weighted 0-10 score, and monitors quality changes to spot regressions or improvements.

Automated code health checking works for pre-ship validation by running a full quality check before shipping new features. It automatically executes available type checkers, linters, and dead code detectors to quickly assess if your codebase has introduced quality issues.

The best way to run multiple linters and test runners without installing extra dependencies is using a tool with zero dependencies that automatically detects your existing configured tools. It executes your available type checkers, dead code detectors, and shell linters, then aggregates their outputs.

Your project needs a single health score because manually aggregating individual results from type checkers, linters, and test suites into an actionable quality metric is tedious. A weighted 0-10 composite score simplifies trend tracking and pre-ship validation.