calculate-coverage
About
The `calculate-coverage` skill measures test coverage percentages and identifies untested code paths to assess test completeness. It helps developers check coverage for modules, identify gaps in test suites, and enforce coverage thresholds. Use it when planning additional test cases or ensuring comprehensive testing of your codebase.
Quick Install
Claude Code
Recommendednpx skills add majiayu000/claude-skill-registry -a claude-code/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/calculate-coverageCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
when-mapping-dependencies-use-dependency-mapper
OtherThis skill provides comprehensive dependency mapping and analysis for software projects across multiple package managers. It extracts dependency trees, detects issues, audits for vulnerabilities, and generates visualizations. Use it when you need to understand, analyze, or visualize project dependencies and their security implications.
Summarizer
OtherThe Summarizer Skill condenses large text content into concise summaries, supporting bullet-points, paragraphs, or executive-summary formats. It analyzes text to identify key themes and main points while removing redundancy. Developers should use it for efficient content processing when they need to extract essential information from lengthy documents.
agent-ops-context-map
OtherThis skill analyzes your codebase to generate a structured, LLM-optimized overview in `.agent/map.md` for efficient project understanding. It features confidence-based staleness thresholds that determine when to refresh the map before implementation work. The map is automatically updated when stale and integrates with other agent-ops skills for coordinated project analysis.
agent-ops-dogfood
OtherThis skill analyzes a project's public documentation to create a verified usage baseline without reading source code. It enforces a strict docs-first approach, identifying gaps by comparing stated claims against actual usage instructions. Use it at project inception to dogfood and establish a human-approved foundation for user guides.
