coveragelisted

# Coverage Skill Determine mode from user intent, then execute. | User wants to... | Mode | Key phrases | |-------------------|------|-------------| | Fix classes with low test coverage | **Fix** (below) | coverage fix, low coverage, improve coverage | | Add/maintain coverage threshold in CI | **Gate** (below) | coverage gate, coverage threshold, enforce coverage | | Audit coverage.config.xml for drift | **Config Audit** (below) | audit coverage config, coverage config drift, coverage.config.xml | If ambiguous, ask which coverage task they need. --- ## Mode: Fix Parse coverage output, identify lowest-covered classes, route to `fill-test-gaps` for test generation. ### Input Formats Accepts three formats (pasted as `$ARGUMENTS` or message body): - **Format A: Spectre Console ANSI** — `[#hex]- NN.N%[/] ClassName` - **Format B: Pipe/tab table** — `| Class | Line Coverage | Branch Coverage |` - **Format C: Summary text** — `ClassName NN.N%` ### Workflow 1. **Parse input** — extract `(class_name, coverage_percentage)` pairs 2. **Rank and filter** — sort ascending, remove 100% and test classes, take bottom 15 3. **Present selection** — show ranked list, ask: "Which classes? (numbers, 'all', or 'top 5')" 4. **Locate source files** — `scripts/find.sh --class {ClassName}` 5. **Dispatch to fill-test-gaps** — spawn agents (up to 3 parallel) for selected classes 6. **Summary** — report before coverage + tests generated ### Rules - Never skip the selection prompt - Parallel