skills.rest
seqis
seqisCOMMUNITY
Explore all skills by this author →
GitHub

agent-coverage-auditor

Analyze test coverage, identify gaps, and enforce quality gates.

Updated Aug 23, 2026
Search Tags:#code quality#testing#regression#coverage#test gaps#auditor
One-click install
npx skills add https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code --skill agent-coverage-auditor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-coverage-auditor
Source: https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code/tree/main/skills_tree/agent-coverage-auditor
Command: npx skills add https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code --skill agent-coverage-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill identifies and analyzes gaps in test coverage, highlighting areas of risk and ensuring comprehensive code quality.

Core Features & Use Cases

  • Test Coverage Analysis: Measures line and branch coverage against defined thresholds.
  • Gap Identification: Pinpoints uncovered critical paths and high-risk code.
  • Regression Detection: Compares current coverage against baselines to detect drops.
  • Use Case: After a code change, use this skill to ensure all new code meets the 90% coverage requirement and that critical payment functions remain at 100% coverage.

Quick Start

Analyze the test coverage for the current project and report any files below the 70% line coverage threshold.

Frequently Asked Questions about agent-coverage-auditor

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

FAQPage Schema
How do I find untested critical paths in my codebase?▼

Test coverage gap identification analyzes line and branch metrics to pinpoint untested critical paths. By comparing current coverage against baselines, it highlights high-risk code and recommends specific test additions.

How do I detect test coverage regressions after a code change?▼

Detect test coverage regressions by comparing current coverage metrics against established baselines. This highlights coverage drops, ensuring new code changes meet threshold requirements without degrading existing quality gates.

Can I enforce a 90% code coverage requirement for new code?▼

Yes, you can enforce a 90% code coverage requirement by configuring quality gates. The analysis measures line and branch coverage against defined thresholds, ensuring new code meets specific percentage requirements.

What is the best way to ensure critical payment functions maintain 100% coverage?▼

The best way to maintain 100% coverage for critical payment functions is through gap identification and quality gates. This enforces strict threshold requirements and highlights untested critical paths immediately.

How do I check if my project files meet a 70% line coverage threshold?▼

Check project line coverage thresholds by running a test coverage analysis. This reports any files falling below the 70% line coverage requirement and identifies specific test gaps to fix.

Why does test coverage drop when adding new code without sufficient tests?▼

Test coverage drops because new untested code increases the total codebase size while the tested portion remains unchanged. Regression detection catches this by comparing current metrics against established baselines.

Related Skills

Explore More Software Engineering Skills→
el-feoel-feo
12

simplecov

Identify coverage gaps in Ruby and Rails projects using SimpleCov.

Community
Advanced
GainInsightDevGainInsightDev

af-test-coverage

Analyze Jest coverage reports to identify untested code paths.

Official
Intermediate
markus41markus41
18

upgrade-analysis

Analyze source files for upgrade opportunities and code quality issues.

Community
Advanced
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate