health

To run a code quality check, execute the command `run health`. This triggers a comprehensive dashboard that computes a weighted composite score by integrating type checkers, linters, test runners, and dead code detectors.

A weighted composite score aggregates results from type checkers, linters, test runners, and dead code detectors into a single metric. This score provides a quantifiable overview of your codebase health and identifies areas for improvement.

Yes, you can track code quality trends over time. The Skill keeps a record of your historical quality scores, allowing you to identify patterns, monitor progress, and assess the long-term health of your codebase.

The dashboard integrates with existing project tools including type checkers, linters, test runners, and dead code detectors. It aggregates their outputs to compute the composite health score without replacing them.

You need a weighted code quality score during software development workflows requiring ongoing maintenance. It is useful when you need a quick health check, a detailed quality score, or a thorough review before major releases.

Automated checks rely on the configuration and coverage of your existing type checkers, linters, and test runners. The composite score reflects tool outputs and may not capture architectural flaws or business logic issues not covered by these integrations.