skills.rest
rakovi4
rakovi4COMMUNITY
Explore all skills by this author →
GitHub

test-coverage

Run tests and report coverage filtered by module, class, or new code changes.

45|13|Updated Apr 13, 2026
Search Tags:#code quality#testing#test coverage#development tools#source code analysis
One-click install
npx skills add https://github.com/rakovi4/continue-framework --skill test-coverage-rakovi4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-coverage
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/test-coverage
Command: npx skills add https://github.com/rakovi4/continue-framework --skill test-coverage-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive test coverage analysis, identifying untested lines and branches in your codebase, ensuring quality and reliability.

Core Features & Use Cases

  • Coverage Analysis: Detect uncovered lines and branches in classes.
  • Custom Reports: Filter and focus on specific modules or classes.
  • Focus on New Code: Report only changes made since the last commit.
  • Use Case: After implementing new functionality, run this Skill to verify that the code is fully covered and that all paths have been tested.

Quick Start

Check test coverage for a specific module using: /test-coverage module

Frequently Asked Questions about test-coverage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check test coverage for specific modules or classes in my codebase?▼

You can check test coverage for specific modules or classes by filtering the analysis to target only those sections. This detects uncovered lines and branches within the focused scope rather than the entire project.

Can I report test coverage on just the new code changes since the last commit?▼

Yes, you can report test coverage on just the new code changes since the last commit. This focuses the analysis exclusively on recently implemented functionality to verify all new paths are tested.

What is the best way to identify untested lines and branches in source code?▼

The best way to identify untested lines and branches in source code is by running a coverage analysis tool that integrates with your test frameworks. It determines untested sections by analyzing the source code directly.

Does this test coverage analysis require any specific dependencies to run?▼

No, this test coverage analysis does not require any specific dependencies to run. It operates independently to integrate with your test frameworks and analyze source code for gaps.

When should I run a test coverage report during the development workflow?▼

You should run a test coverage report during development immediately after implementing new functionality. This verifies that the newly added code is fully covered and that all execution paths have been tested.

Related Skills

Explore More Software Engineering Skills→
ArabelaTsoArabelaTso
142

coverage-enhancer

Analyze test suites and source code to suggest unit tests for uncovered branches.

Community
Intermediate
makeupmakeup
47

test-coverage

Evaluate unit test coverage for makeup-js modules and generate prioritized gap reports.

Official
Intermediate
mwathibenmwathiben

typescript-review

Review TypeScript and JavaScript diffs against Metabase coding standards.

Community
Intermediate
copyleftdevcopyleftdev

lipton-mutation-testing

Inject faults into source code and calculate mutation scores for test suites.

Community
Advanced