skill-coverage-audit

Analyze source code to identify untested paths and generate tests.

28|3|Updated May 10, 2026
One-click install
npx skills add https://github.com/CES-Ltd/Lumi --skill skill-coverage-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-coverage-audit
Source: https://github.com/CES-Ltd/Lumi/tree/main/resources/seed/octopus/skills/skill-coverage-audit
Command: npx skills add https://github.com/CES-Ltd/Lumi --skill skill-coverage-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers verify the completeness of their test coverage by analyzing codepaths, mapping existing tests, and identifying untested scenarios, ensuring software reliability.

Core Features & Use Cases

  • Codepath Analysis: Trace code execution paths in changed files including error and condition branches.
  • Test Mapping: Find and evaluate existing tests related to the code under review.
  • Coverage Visualization: Generate ASCII summaries showing tested vs untested paths.
  • Auto-Generate Tests: Create new test cases for uncovered codepaths following project conventions.
  • Use Case: When preparing for deployment, a developer runs this Skill to identify untested error handling paths and automatically generate the missing tests to improve quality.

Quick Start

Invoke the skill with your code diff or source directory and review the coverage report to see gaps and suggested tests.

Frequently Asked Questions about skill-coverage-audit

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

FAQPage Schema
How do I find untested code paths in my source code?

To find untested code paths, you analyze source code execution branches, map existing tests against them, and generate a coverage report highlighting gaps in error and condition branches.

Can I automatically generate test cases for uncovered code?

Yes, automated testing tools can auto-generate new test cases for uncovered codepaths, following your project conventions to improve software test coverage and robustness without manual effort.

How does codepath analysis work for error and condition branches?

Codepath analysis traces execution paths in changed files, evaluating both standard logic and specific error or condition branches to ensure all critical execution routes are tested.

What is the best way to map existing tests to changed source files?

The best way to map existing tests is to use an automated tool that evaluates tests related to the code under review, matching them to execution paths to visualize tested versus untested scenarios.

Do I need to provide a code diff to run a test coverage analysis?

You can invoke the test coverage analysis using either a specific code diff or your entire source directory, allowing the tool to trace execution paths and generate missing tests for deployment preparation.

How do I visualize tested versus untested paths in my codebase?

You can visualize tested versus untested paths by generating ASCII summaries that map existing tests against traced codepaths, providing a clear text-based report of your current test coverage gaps.