maintaining-full-coverage

Enforce 100% test coverage and commit TEST-REPORT.md with git hash.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mtschoen/maintaining-full-coverage --skill maintaining-full-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintaining-full-coverage
Source: https://github.com/mtschoen/maintaining-full-coverage/tree/main/skill-draft
Command: npx skills add https://github.com/mtschoen/maintaining-full-coverage --skill maintaining-full-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures engineers do not declare work complete until every line of production code in the repository is exercised by tests and recorded in a checked-in coverage report, preventing silent coverage regressions and "close enough" thinking.

Core Features & Use Cases

  • Repository-wide coverage gate: Verifies 100% coverage across all languages and modules before allowing completion, commit, or merge.
  • Checked-in reporting: Requires generating and committing a TEST-REPORT.md (or equivalent) with git hash, test counts, and coverage numbers so regressions are visible via git diff.
  • Escalation ladder: Provides an ordered workflow from writing tests to heroic testing, asking a human, framework exclusions with approval, and documented exceptions as a last resort.
  • Use case: When finishing a feature that touches backend and frontend code, run coverage for each language, fix uncovered lines, and commit a TEST-REPORT.md so CI and reviewers can immediately detect regressions.

Quick Start

Run the repository's coverage commands for all languages, confirm 100% statements coverage, write or update TEST-REPORT.md with the git short hash and test counts, and commit it before claiming the work is done.

Frequently Asked Questions about maintaining-full-coverage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce 100% test coverage before merging a pull request?

Enforce 100% test coverage by running a fresh full coverage pass across all repository languages, fixing uncovered lines, and committing a TEST-REPORT.md with the git hash and test counts alongside your changes before declaring work complete.

How do I track test coverage regressions across multiple programming languages in one repository?

Track multi-language coverage regressions by running language-specific coverage commands, confirming 100% statements coverage, and maintaining a checked-in TEST-REPORT.md so any coverage drop is immediately visible via git diff during code review.

What should I do when I cannot reach full test coverage for certain lines?

When full coverage cannot be reached, follow an escalation ladder: write more tests, attempt heroic testing, ask a human, apply framework exclusions with approval, and document exceptions as a last resort before committing the final TEST-REPORT.md.

Does this 100% coverage gate work for repositories with multiple programming languages?

Yes, the coverage gate works for multi-language repositories by locating or constructing the specific coverage commands required for each language, running a fresh full coverage pass, and aggregating the results into a single checked-in TEST-REPORT.md.

How do I generate a test coverage report that blocks CI pipelines on regressions?

Generate a CI-blocking coverage report by running full coverage for all languages, verifying 100% statements coverage, and writing a TEST-REPORT.md with the git hash and test counts that CI can inspect to detect silent regressions before merge.