agentleFS
TheophilusChinomonaTheophilusChinomona/idev/skills/test-coverage/SKILL.md

test-coverage

Skill0 starsChanged 5 months agoMITView on GitHub

Measures and reports test coverage for the project. Use when asked about coverage, before PRs, or when coverage drops.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • qtzx06Skill

    eval

    Evaluate trained YOLO model accuracy with mAP metrics and per-class error analysis. Identifies failure cases for targeted improvement. Use after training.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    iterative-retrieval

    Max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation. Use when spawning sub-agents to complete scoped work.

    Also in 3 projects that use this

  • iovisorSkill

    evolve

    Evolve uBPF through a gated spec-first workflow that propagates approved changes through requirements, design, validation, implementation, and RFC alignment artifacts.

    Also in 3 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before creating a PR

    line 13
  2. Distinctive:

    When coverage drops below threshold

    line 14
  3. Distinctive:

    Do NOT skip coverage on "simple" files

    line 64
  4. Distinctive:

    Do NOT mock everything — integration tests need real calls

    line 65
  5. Distinctive:

    Do NOT ignore coverage drops — investigate and fix

    line 66

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Coverage Skill

Purpose

Measure, report, and enforce test coverage thresholds.

Activation

  • User says "check coverage" or "what's the coverage?"
  • Before creating a PR
  • When coverage drops below threshold

How It Works

1. Detect Test Framework

JavaScript/TypeScript:
  jest.config.* → npx jest --coverage
  vitest.config.* → npx vitest --coverage
  .nycrc → npx nyc report

Python:
  pytest.ini → pytest --cov
  pyproject.toml [tool.pytest] → pytest --cov

.NET:
  *.Tests.csproj → dotnet test /p:CollectCoverage=true

2. Run Coverage

# JavaScript/TypeScript
npx jest --coverage --coverageReporters=text-summary

# Python
pytest --cov=src --cov-report=term-missing

# .NET
dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=lcov

3. Report

Coverage Report
═══════════════
Lines:    85% (120/141)
Branches: 78% (45/58)
Functions: 92% (33/36)

Below 80% threshold:
  src/auth.ts: 65% (missing edge cases)
  src/utils.ts: 72% (missing error paths)

Threshold

  • Minimum: 80% line coverage
  • Target: 90% line coverage
  • Branches: 75% minimum

Anti-Patterns

  1. Do NOT skip coverage on "simple" files
  2. Do NOT mock everything — integration tests need real calls
  3. Do NOT ignore coverage drops — investigate and fix

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.