Risk-prioritised test coverage analysis — find the most dangerous untested code
From chaosnpx claudepluginhub jackscammell/parliament-of-chaos --plugin chaosGo beyond numeric coverage percentages. Run tests with coverage instrumentation, then classify uncovered code by risk to produce a prioritised list of what needs testing most.
/coverage-audit [--generate] [--threshold <percent>]
Examples:
/coverage-audit # Analyse coverage and prioritise gaps
/coverage-audit --generate # Analyse gaps then generate tests for top priorities
/coverage-audit --threshold 80 # Flag modules below 80% coverage
--generate (optional): After analysis, auto-generate tests for the highest-risk uncovered code (chains to /generate-tests)--threshold (optional): Minimum coverage percentage to flag modules below (default: no threshold, prioritise by risk)Run Coverage
Identify Uncovered Code
Classify by Risk
Prioritise
Generate (if --generate)
/generate-tests workflow# Coverage Audit
**Overall**: 72% line coverage, 58% branch coverage
## Top 10 Untested Critical Paths
| # | File | Function | Risk | Lines |
|---|------|----------|------|-------|
| 1 | src/auth/verify.ts | verifyToken() | Critical | 15 uncovered |
| 2 | src/payments/charge.ts | processPayment() | Critical | 23 uncovered |
## Modules Below Threshold
| Module | Coverage | Gap |
|--------|----------|-----|
| src/auth/ | 45% | 35% below threshold |
/generate-tests --coverage-gaps for automated gap filling