Pytest coverage
Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%.From its SKILL.md
npx -y skills add mouadja02/skills --skill pytest-coverageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 224 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most unit integration skills give in 224 tokens
Counted across 149 of the 202 authors here whose files we hold, read 2026-09-06
- Structure tests as arrange, act, assertin 17 of 149
- Test behavior, not implementationin 16 of 149
- Mock all external dependenciesin 14 of 149
- Keep tests independentin 9 of 149
- Implement minimal code to passin 7 of 149
- Write a failing test firstin 7 of 149
- Fix or delete flaky tests immediatelyin 7 of 149
- Verify one behaviour per test functionin 7 of 149
- Name tests MethodName_StateUnderTest_ExpectedBehaviorin 6 of 149
- Separate arrange, act, and assert with blank linesin 6 of 149
- Target at least 80 percent core logic coveragein 6 of 149
- Create factory fixtures for test datain 6 of 149
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.