calculate-coverage
Measure test coverage and identify untested code. Use when assessing test completeness.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install mvillmow-projectodyssey-calculate-coverage
Repository
Skill path: .claude/skills/tier-2/calculate-coverage
Measure test coverage and identify untested code. Use when assessing test completeness.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack, Testing.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: mvillmow.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install calculate-coverage into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/mvillmow/ProjectOdyssey before adding calculate-coverage to shared team environments
- Use calculate-coverage for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: calculate-coverage description: "Measure test coverage and identify untested code. Use when assessing test completeness." mcp_fallback: none category: analysis tier: 2 --- # Calculate Coverage Measure code coverage percentage and identify which code paths are untested to ensure comprehensive testing. ## When to Use - Checking test coverage for modules - Identifying gaps in test suites - Meeting coverage thresholds (typically 80%+) - Planning additional test cases ## Quick Reference ```bash # Python coverage with pytest pip install coverage pytest-cov pytest --cov=module_name --cov-report=html tests/ # View coverage report open htmlcov/index.html # Check coverage threshold coverage report --fail-under=80 ``` ## Workflow 1. **Install coverage tool**: Set up measurement infrastructure 2. **Run tests with coverage**: Execute test suite capturing coverage data 3. **Generate report**: Create HTML or text coverage report 4. **Analyze gaps**: Identify untested functions, branches, edge cases 5. **Plan improvements**: Create tests for uncovered code paths ## Output Format Coverage analysis: - Overall coverage percentage - Per-module coverage breakdown - Uncovered lines (with line numbers) - Branch coverage (if applicable) - Recommendations for improvement ## References - See `run-tests` skill for test execution - See `generate-tests` skill for test creation - See CLAUDE.md > Key Development Principles (TDD) for testing strategy