boost-coverage

Iteratively raise repository coverage by discovering coverage commands and adding targeted tests.

9|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/conn-castle/agent-layer --skill boost-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boost-coverage
Source: https://github.com/conn-castle/agent-layer/tree/main/internal/templates/skills/boost-coverage
Command: npx skills add https://github.com/conn-castle/agent-layer --skill boost-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Raise coverage iteratively by discovering the repo's real coverage commands, selecting the next eligible low-coverage file, adding tests, and repeating until the documented threshold is met or a high-value blocker requires human input.

Core Features & Use Cases

  • Discover coverage contracts and commands across CI configs and test suites.
  • Identify eligible low-coverage files and target them with small, reviewable tests.
  • Iterate until coverage thresholds are met, or blockers require human input.
  • Use multi-agent coordination to plan, execute, and verify coverage improvements.

Quick Start

Run the boost-coverage skill to begin iterative coverage improvement in your repository.

Frequently Asked Questions about boost-coverage

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

FAQPage Schema
How do I iteratively boost test coverage in my software repository?

To boost test coverage iteratively, this Skill automates discovering real coverage commands across CI configs, targets eligible low-coverage files with small tests, and repeats until a documented threshold is met. It applies multi-agent coordination to plan, execute, and verify each improvement.

How does automated test generation find low-coverage files in a CI pipeline?

Automated test generation finds low-coverage files by discovering the repository's real coverage contracts and commands across existing CI configurations and test suites. It then identifies eligible files and targets them with small, reviewable tests to iteratively raise coverage.

Can I use automated test generation for repositories without a CI pipeline?

No, this automated test generation applies specifically to software repositories with existing CI pipelines and test suites. It relies on discovering real coverage contracts from those CI configurations to identify eligible low-coverage files and guide targeted test additions.

What is the best way to enforce a coverage threshold and stop test generation automatically?

The best way to enforce a coverage threshold is to let the Skill iterate until the documented threshold is met or a high-value blocker requires human input. It outputs an iteration digest to a designated path and stops automatically upon reaching the target.

Why does iterative coverage improvement stop before reaching full coverage?

Iterative coverage improvement stops before full coverage when a high-value blocker requires human input. The Skill enforces a documented coverage threshold to stop, ensuring it halts at the target or when it cannot automatically resolve an issue.

Does the boost-coverage Skill work with existing quality-assurance and test-generation workflows?

Yes, the boost-coverage Skill works with existing quality-assurance workflows by discovering real coverage contracts from current CI configs and test suites. It guides targeted test additions using multi-agent coordination to plan, execute, and verify improvements.