coverage-check

Validates test coverage thresholds from nyc and Jest reports in CI pipelines and pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Techlemariam/IronForge --skill coverage-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coverage-check
Source: https://github.com/Techlemariam/IronForge/tree/main/.agent/skills/coverage-check
Command: npx skills add https://github.com/Techlemariam/IronForge --skill coverage-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, npm, and includes scripts (resource) components.

What problem does it solve?

Validates that test coverage meets minimum thresholds to prevent undetected regressions and maintain code quality.

Core Features & Use Cases

  • Automated coverage threshold checks across statements, branches, functions, and lines.
  • CI-friendly verification with clear pass/fail outcomes and actionable feedback.
  • Cross-platform support (Windows, Linux, macOS) for diverse development environments.

Quick Start

Run the coverage check in your CI or local environment to verify current test coverage against the defined thresholds.

Frequently Asked Questions about coverage-check

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

FAQPage Schema
How do I validate test coverage thresholds in a CI pipeline?

Check test coverage thresholds locally by running the validation scripts against available coverage data from Jest or nyc, comparing statements, branches, functions, and lines against your configured minimums to return a clear pass or fail outcome.

Does test coverage validation work across different operating systems?

Test coverage validation requires Node and npm installed to execute the scripts, providing cross-platform support across Windows, Linux, and macOS environments for diverse development setups.

What metrics are checked when validating code coverage limits?

Code coverage limits are checked across statements, branches, functions, and lines by parsing reports from tools like nyc and Jest, ensuring all measured dimensions meet the defined thresholds to prevent undetected regressions.

Why do I need to enforce minimum coverage thresholds in pull requests?

Enforce minimum coverage thresholds in pull requests to prevent undetected regressions and maintain code quality, applying automated checks that parse coverage data and emit actionable pass or fail feedback before merging.

Can I use PowerShell scripts to automate coverage checks?

Automate coverage checks using PowerShell scripts to parse coverage reports from tools like Jest and nyc, comparing the data against required thresholds and emitting clear pass or fail outcomes for CI pipelines and local development.