karvey-healthlisted

# karvey-health — Code quality dashboard A **cross-cutting** skill of the Karvey Method. It is a **support layer, NOT a phase**: it can be invoked at any point in the cycle and **does NOT modify** `spec.json:phase` nor advance the method. Inspired by gstack's `/health`. ## Purpose Deliver a **continuous and comparable code-health metric** per repo: a single 0–10 score that summarizes the state of the type checker, the linter, the tests and dead-code detection, together with its **trend over time** and prioritized recommendations to raise the score. The goal is that anyone on the team can ask "how is the repo's health?" and get an objective, repeatable answer that is comparable across runs. ## When it is used - On demand (`karvey health`). - As a support check before or after any phase (requirements, design, implementation, test, deploy), without altering the phase state. - In any repo, **stack-agnostic**. ## Steps ### 1. Detect the stack and the available tools Inspect the repo (or the path from the `[<repo or path>]` argument; if none is passed, use the current repo) to identify language, package manager and the available quality tools. **Stack-agnostic** — detect by configuration files and manifests, do not assume a language: - **Type checker**: `tsc`/TypeScript (`tsconfig.json`), `mypy`/`pyright` (Python), `go vet`/compiler (Go), `flow`, etc. - **Linter**: `eslint`, `biome`, `ruff`/`flake8`/`pylint` (Python), `golangci-lint`, `clippy` (Rust), etc. - **Test runner