check-coverage
Run test coverage measurement, analyze results, and fix gaps when coverage falls below the 80% threshold.
Best use case
check-coverage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run test coverage measurement, analyze results, and fix gaps when coverage falls below the 80% threshold.
Teams using check-coverage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/check-coverage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How check-coverage Compares
| Feature / Agent | check-coverage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run test coverage measurement, analyze results, and fix gaps when coverage falls below the 80% threshold.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Check Coverage ## Steps ### 1. Run `make test-cov-check` If tests pass and coverage >= 80%, done. ### 2. If tests fail - **Existing tests broke**: fix production code, not tests. - **New tests fail**: fix the test. - **Ambiguous**: read test intent. If behavior intentionally changed, update test and document in commit message. ### 3. If coverage below 80% Check "Missing" column. Prioritize: 1. New code you just wrote (must have tests). 2. Critical paths (error handling, validation, CLI logic). 3. Utility functions with clear contracts. Do NOT: add trivial tests just to raise numbers, add `# pragma: no cover` without justification, or test third-party/Streamlit internals. ### 4. Write tests Add to `tests/test_<module>.py`. Use `project_layout` fixture when needed. One behavior per test function. ### 5. Re-run `make test-cov-check` Repeat until threshold met. ### 6. HTML report (optional) `make test-cov` -- opens `htmlcov/index.html`. ## Failure handling - Missing `pytest-cov`: run `uv sync --dev`. - Uncoverable lines (platform-specific, external calls): add `# pragma: no cover` with reason, note in commit message.
Related Skills
check-pr-comments
Fetch unresolved PR review threads, triage them, implement fixes, validate, reply in-thread, and resolve.
write-tests
Write or update unit tests for changed code, following project conventions and ensuring coverage meets the 80% threshold.
update-pr
Stage, commit, and push follow-up changes to an existing feature branch or PR. Use for quick iterations.
setup-environment
Set up or verify the local development environment. Use when starting work in a fresh clone or new machine, when commands fail with missing dependencies or broken imports, or before running `make check`/`make test` for the first time in a session.
review-architecture
Review architecture quality, maintainability, and developer experience.
make-yt-issue
Ensure a YouTrack issue exists before starting work. Validates existing tickets or creates new ones.
local-code-review
Review local code changes for correctness, regressions, missing tests, and Databao-specific risks.
eval-skills
Run structured evaluations on skills to measure quality and track improvements.
create-pr
Stage, commit, push, and open a GitHub PR following project conventions. Use when code is ready to ship.
create-branch
Create a feature branch following project naming conventions. Use when starting work on a ticket, after understanding the scope, or when the agent needs to branch off main for new work.
autosteer
Run the full development pipeline autonomously without pausing between phases. Stops only on quality-gate failures.
ward-identity-checker
Ward Identity Checker