pytest-coverage
Skill129 starsChanged 5 months agoApache-2.0View on GitHub
Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%.
6 other projects use a version of this; 1 new project in the last 4 weeks, against 0 the 4 before.
Adopted by
Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- theexperiencecompany/gaiaword for word, first seen Nov 13, 2026
- docdyhr/simplenote-mcp-serverword for word, first seen Nov 1, 2026
- github/awesome-copilotword for word, first seen Oct 25, 2026
- calf-ai/calfkit-sdkword for word, first seen Jun 20, 2026
- ryan-yuuu/crypto-trading-arenaword for word, first seen Jun 17, 2026
- ReaperOAK/ForgeOSword for word, first seen Jun 8, 2026
Other versions6 projects use a version of this.
Word for word · 6
- github/awesome-copilot★ 41k100% same
- theexperiencecompany/gaia★ 327100% same
- calf-ai/calfkit-sdk★ 146100% same
- ryan-yuuu/crypto-trading-arena★ 127100% same
- docdyhr/simplenote-mcp-server★ 21100% same
- ReaperOAK/ForgeOS★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- diataxis-docs-writerSkill
- grill-with-docsSkill
- test-driven-developmentSkill
- uvSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Distinctive: line 12
If you are checking for coverage of a specific module, you can specify it like this:
- Distinctive: line 25
If a line starts with a ! (exclamation mark), it means that the line is not covered by tests.
- Distinctive: line 26
Add tests to cover the missing lines.
- Distinctive: line 28
Keep running the tests and improving coverage until all lines are covered.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The goal is for the tests to cover all lines of code.
Generate a coverage report with:
pytest --cov --cov-report=annotate:cov_annotate
If you are checking for coverage of a specific module, you can specify it like this:
pytest --cov=your_module_name --cov-report=annotate:cov_annotate
You can also specify specific tests to run, for example:
pytest tests/test_your_module.py --cov=your_module_name --cov-report=annotate:cov_annotate
Open the cov_annotate directory to view the annotated source code. There will be one file per source file. If a file has 100% source coverage, it means all lines are covered by tests, so you do not need to open the file.
For each file that has less than 100% test coverage, find the matching file in cov_annotate and review the file.
If a line starts with a ! (exclamation mark), it means that the line is not covered by tests. Add tests to cover the missing lines.
Keep running the tests and improving coverage until all lines are covered.
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.

