What problem does it solve?
This Skill solves the fragmented code quality problem where teams run type checkers, linters, and test suites separately and struggle to synthesize results into a clear health assessment. It eliminates the manual effort of aggregating disparate tool outputs by computing a single weighted composite score and tracking trends over time, so teams know if code quality is improving or slipping.
Core Features & Use Cases
- Composite Health Scoring: Aggregates type checking, linting, test coverage, dead code detection, and shell script hygiene into a weighted 0-10 score.
- Trend Tracking: Records quality metrics over time to visualize whether the codebase is improving or degrading across commits.
- Use Case: A staff engineer preparing for a quarterly planning meeting can run this Skill to get a single health metric, identify which quality dimension is regressing, and make a data-driven case for allocating time to technical debt.
Quick Start
Use the health skill to run all available code quality checks and generate a composite health score for the current project.