test-coveragelisted

## STOP - Read before ANY tool call 1. Read `{{GUARDRAILS_PATH}}` 2. Read `_shared/sdd-artifacts/SESSION.md`; load session-state for `$Cwd` 3. If the relevant gate is not approved: **STOP** - ask user **(pt-BR)** - do **NOT** Write/Shell 4. SDD/develop skills: after **ONE** step/task, **STOP** session - handoff only 5. This skill body is **English**; user-facing prompts may be **(pt-BR)** ### Step -1 - Gate check (report in chat before continuing) ``` Gate check: [ ] guardrails.mdc read [ ] SESSION.md read; session-state loaded [ ] PIPELINE.md read (SDD skills only) [ ] User confirmed current action (sim) -> If any unchecked: STOP ``` --- ## Trigger Invoke when the user asks for: `/test-coverage`, `coverage report`, `coverage`, or when a PLAN step / `code-review` requires coverage evidence. **Arguments (optional):** | Input | Meaning | |-------|---------| | Base branch | `main`, `develop` - ask once if missing (same as `code-review`) | | Test project path | `path/to/Tests.csproj` - auto-detect `*Tests.csproj` / `*.Tests.csproj` if omitted | | Threshold | Minimum line coverage on **changed production `.cs` files** (default: **80**) | | Target | **100** - aspirational; document gaps when below 100 but >= threshold | ## Outcome A structured **coverage report** in **pt-BR** with: - **Coverage on new code** - line coverage on changed production files vs base branch - **Overall branch coverage** - solution-wide line coverage after tests - **Per-file breakdown** - each ch