health

A code health score aggregates results from type checking, linting, testing, and dead code detection to generate a weighted 0-10 rating. This provides a single metric to evaluate and track codebase quality consistently across commits.

Tracking code quality regressions in CI pipelines involves running static analysis and tests across commits to analyze health score trends. This enables automated alerting when quality metrics drop, helping teams spot regressions proactively.

Yes, you can run static analysis and type checking locally to monitor codebase health. The analysis logic supports local development environments alongside CI pipelines, allowing developers to evaluate code quality before pushing commits.

Code health scoring is designed for large repos and supports trend analysis across multiple branches. By aggregating metrics like lint errors and dead code, it enables proactive health monitoring and quantifies improvements over time.

No specific linters or test runners are mandated; the skill implements extensible wrapping logic to integrate various type checking, linting, and testing tools. Optional scripts and assets can augment this analysis to fit your existing workflow.