← ClaudeAtlas

noyalib-coverage-campaignlisted

Raise noyalib line, branch, and function coverage toward the 98% target. Use for 'raise coverage', llvm-cov gaps, coverage-gap triage, ratcheting fail-under thresholds, or picking the next coverage target. Fences off the known wrong turns (chasing 100%, weakening thresholds).
sebastienrousseau/agtmls · ★ 1 · AI & Automation · score 80
Install: claude install-skill sebastienrousseau/agtmls
# noyalib-coverage-campaign **Purpose.** Run the coverage-hardening campaign to specification, unsupervised, on a Sonnet-class session. This skill is the *decision procedure*, not a tutorial: at each phase there is a command, an expected observation, and a gate that says whether to proceed, retry, or escalate. **Scope guard.** This skill covers only the coverage campaign. For the wider "how do we test noyalib at all" question (test layers, proptest, fuzz, Miri, spec suite) use **noyalib-validation-and-qa**. For interpreting a specific tool's output (llvm-cov flags, cargo-vet, deny) use **noyalib-diagnostics-and-tooling**. Do not duplicate those skills here. **Progressive disclosure.** This SKILL.md is the campaign spine. Extended material — bucket-classification walkthroughs, verbatim house-pattern snippets, "why not" rationale for each fenced wrong-path, expanded solution-menu prefer-when notes, and the `invariant_violated` file:line inventory — is in [`reference.md`](./reference.md). Load `reference.md` when the compact guidance below is insufficient; each section flags its cross-reference. --- ## 0. Baseline numbers (VOLATILE — re-verify at campaign start) Captured 2026-07-08 from `.github/workflows/ci.yml:160-162`, `.github/workflows/shared-coverage.yml` reusable defaults, `doc/TESTING.md` §"Coverage gate", and PLAN.md §1 "Coverage baseline": | axis | live workspace gate (`ci.yml`) | shared-coverage.yml default | `doc/TESTING.md` (stale) | target | |----------