← ClaudeAtlas

module-health-rolluplisted

Test-driven module-health rollup. Issue
Eliyce/paqad-ai · ★ 4 · AI & Automation · score 74
Install: claude install-skill Eliyce/paqad-ai
## What It Does Runs the test-driven module-health rollup defined by issue #80, Phase 3. For every module declared in `module-map.yml`, the rollup computes: | Metric | Source | | -------------------- | --------------------------------------------------------------- | | `coverage_pct` | Coverage report parsed via the pack's `coverage_format` parser. | | `tests_passing` | Test report parsed via the pack's `test_report_format` parser. | | `tests_failing` | Same. | | `tests_total` | Same. | | `change_velocity` | `git log -- <sources>` over `git_window_days` (default 14). | | `contract_stability` | `public_api_extractor` output. Blocked when extractor absent. | Coverage and test rows are attributed to module slugs by matching each file against `module-map.yml`'s `sources:` globs. Files that match no module land in the report's `unattributed_files` list (surfaced to the user as a `MM-ADD` candidate for the reconciler). Hard rule: no metric is fabricated or zeroed. When a signal cannot be computed the metric is set to `null` and the reason recorded in `blocked_metrics` (e.g. `coverage:not_configured`, `tests:report_missing:<path>`, `contract_stability:no_public_api_extractor`). ## Use This When - `feature-development.checks` finishes format/test/build and needs