coverage
Skill1 starsChanged 3 days agoMITView on GitHub
Measure and raise the test coverage of a C / C++ project built the cpp-tests way (GoogleTest, tests/ + BUILD_TESTS, unit_tests) - instrumented build in a copy (clang source based coverage, llvm-profdata / llvm-cov), lines / functions / branches per file, the functions never called and the line ranges never run, then new tests written module by module (cpp-tests rules) and re-measured until the coverage stops growing, and at the end always the question of a report (report skill) on what is still missing and why. Use whenever the user asks for the coverage, what is not tested, to fill / raise / maximize the coverage, or for a coverage report.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- TsukiNi22/skillsword for word, first seen Nov 16, 2026
- LeanMeanCleanApps/CleanLambdaFunctiontheir own version, first seen Nov 15, 2026
- oberemokis/skillstheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanWebApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanGraphQLApitheir own version, first seen Nov 15, 2026
- LeanMeanCleanApps/CleanMinimalApitheir own version, first seen Nov 15, 2026
Used with
Projects with it also use scan, lint and 10 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.
rajnavakotiSkillscan
Run the AI dashboard scanner and generate the HTML report.
Also in 4 projects that use this
Microsoft AzureSkilllint
Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.
Also in 4 projects that use this
julienamorganSkillprofile
Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).
Also in 3 projects that use this
asterkinSkilladr
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
Also in 4 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 3 projects that use this
MicrosoftSkillworktree
Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.
Also in 3 projects that use this
Other versions35 projects use a version of this.
Word for word · 1
- TsukiNi22/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 34
- FalkorDB/FalkorDB★ 11ksame name
- pydantic/monty★ 8.9ksame name
- LiberatedPixelCup/Universal-LPC-Spritesheet-Character-Generator★ 1.9ksame name
- firedancer-io/firedancer★ 1.6ksame name
- hegeldev/hegel-rust★ 400same name
- LeanMeanCleanApps/CleanMinimalApi★ 400same name
- wboayue/rust-ibapi★ 400same name
- nockawa/Typhon★ 253same name
- Amplicode/spring-skills★ 126same name
- AsiaOstrich/universal-dev-standards★ 84same name
24 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- write-like-meSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 30 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Read uncovered.md for the file and the source of the missed ranges (HTML or the file itself).
- Very specific: line 32
Write the tests with cpp-tests (file mirroring the tree, nominal / edge / error cases, libutils error codes, sub-process isolation with …
- Distinctive: line 37
Stop when a pass gains nothing (only what can't be reached is left).
- Very specific: line 47
When the tests are written (or when the user only asked for the measure), always ask (AskUserQuestion, French): Veux-tu un rapport de la …
- Distinctive: line 50
Summary: before / after (lines, functions, branches), tests added, tests failing (known bugs).
“Common” is measured: kept by at least 6 in 10 of the 30 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.
Files
Coverage (cpp-tests projects)
SKILL_DIR = the directory of this file. Requires cpp-tests (the test setup and the rules for writing tests: load it),
report for the final report. Scripts: scripts/coverage.sh (build + run + llvm-cov), scripts/uncovered.py (what is
missing, as tables). Tools: clang++, llvm-profdata, llvm-cov (llvm package: ask before installing, like
benchmark). Nothing is written in the project except the new tests; the build happens in a /tmp copy.
1. Measure (baseline)
bash SKILL_DIR/scripts/coverage.sh <root> --out /tmp/coverage-<name>-before [--html] [--run "./unit_tests --gtest_filter=..."]
python3 SKILL_DIR/scripts/uncovered.py /tmp/coverage-<name>-before --md /tmp/coverage-<name>-before/uncovered.md- No
tests//BUILD_TESTSyet: set them up withcpp-testsfirst (ask the user). - The build is Debug +
-fprofile-instr-generate -fcoverage-mapping(clang), one profile per process (forked tests and sub-processes counted),tests/,/usr,_depsandgenerated_*left out of the numbers (--ignoreto change). - Failing tests don't stop the measure (see
tests.log), but say them: a failing test is a bug or a known bug kept as failing (cpp-testsrule), never "fixed" by weakening the test. summary.txt(per file),uncovered.md(functions never called, line ranges never run),--htmlfor the annotated sources (html/index.html: open it to read which branch is missed).
2. Fill (maximize, module by module)
Order: the files with the most missed lines first, the public API before the internals (an internal reached through the public API needs no direct test). For each module:
- Read
uncovered.mdfor the file and the source of the missed ranges (HTML or the file itself). - Write the tests with
cpp-tests(file mirroring the tree, nominal / edge / error cases, libutils error codes, sub-process isolation with timeout for threads / IPC /exit, mocks of the interfaces,TempDir/ScopedEnv), register them intests/CMakeLists.txt. - Build and run the tests normally (
cmake -B build -DBUILD_TESTS=ON...) until they pass, then re-measure (coverage.shwith the same options) and note the gain of the module. Stop when a pass gains nothing (only what can't be reached is left). What can't (or shouldn't) be covered is listed with its reason, not forced:
- defensive branches of impossible states,
FatalExceptionpaths needing a broken system (allocation / syscall failure: only when a cheap injection exists, ex: a closed fd, an unreadable file); - code that blocks forever, needs hardware / network not available in a test, or is platform specific;
- dead code (never called by anything): report it, propose to remove it, never test it. Never change the production code to raise the coverage. A bug found by a new test: keep the test failing (known bug), tell the user and fix it only on request.
3. End: always ask for the report
When the tests are written (or when the user only asked for the measure), always ask (AskUserQuestion, French):
Veux-tu un rapport de la couverture et de ce qui manque ? · Oui (Recommandé) · Non. If yes, report skill
(format asked there), location audit/<YYYY-MM-DD>-coverage.md|pdf:
- Summary: before / after (lines, functions, branches), tests added, tests failing (known bugs).
- Coverage per file: the table of
uncovered.md(after), with the before column for the files changed. - Still missing: per file, the functions / ranges left and why (the categories above), with what would cover them (refactor for testability, fault injection, integration test).
- Bugs found (if any) and dead code found.
- Reproduce: the
coverage.shcommand.
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
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.

