What problem does it solve? Engineering teams lack a single, repeatable way to measure overall codebase quality, forcing them to run type checkers, linters, tests, and dead-code detectors separately and interpret scattered results. ## Core Features & Use Cases - Unified quality checks: Wraps the project's existing type checker, linter, test runner, dead code detector, and shell linter into one invocation. - Composite scoring: Computes a weighted 0-10 health score from the individual tool results and tracks the trend over time. - Use Case: Before a release, ask for a health check to run all quality gates at once, get a single score, and compare it against previous runs to confirm the codebase is improving rather than regressing. ## Quick Start Ask the agent to run a code health check and show the current quality score for this repository.