coverage-driven-testing

Increase test coverage and identify unreachable code in a monorepo.

3|2|Updated May 12, 2026

Search Tags:#automation #testing #refactoring #monorepo #coverage #dead-code

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill coverage-driven-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coverage-driven-testing
Source: https://github.com/kriscendobot/garden/tree/main/skills/coverage-driven-testing
Command: npx skills add https://github.com/kriscendobot/garden --skill coverage-driven-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of maintaining high-quality test coverage while preventing the accumulation of unreachable, dead code in a monorepo environment.

Core Features & Use Cases

Baseline-and-Iterate Loop: Provides a structured procedure to identify uncovered branches and improve test coverage incrementally.
Dead Code Identification: Uses a rigorous four-criterion threshold to safely identify and remove unused symbols.
Use Case: When a maintainer requests a coverage pass on a specific package, this skill guides the agent to focus on meaningful integration tests rather than superficial unit tests, ensuring the codebase remains lean and reliable.

Quick Start

Run the coverage-driven-testing skill to analyze the current package and identify opportunities for both test improvements and dead code removal.

Frequently Asked Questions about coverage-driven-testing

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

FAQPage Schema

How do I increase code coverage in a monorepo without writing superficial unit tests?▼

To increase code coverage effectively, establish a baseline and iterate by focusing on public-API integration tests rather than superficial unit tests. This approach systematically targets uncovered branches to ensure the monorepo remains reliable.

What is the best way to identify and remove dead code safely?▼

Dead code identification applies a rigorous four-criterion threshold to safely determine symbol reachability. This process validates code unreachability across the monorepo before pruning unused symbols.

How does static analysis validate dead code removal across a monorepo?▼

Static analysis validates dead code removal by integrating with local test runners to confirm code reachability across the monorepo. This integration ensures symbols meet the four-criterion threshold before deletion.

Do I need local test runners to perform coverage-driven testing?▼

Yes, coverage-driven testing requires integration with local test runners and static analysis tools. These dependencies are necessary to validate code reachability and execute the baseline-and-iterate loop.

When should I not use a baseline-and-iterate loop for test coverage?▼

Avoid the baseline-and-iterate loop when superficial unit tests are preferred over public-API integration tests, or when local test runners and static analysis tools are unavailable to validate reachability.