Maintain test coverage thresholds
SkillDev toolstest-coverage is a skill for AI agents that helps maintain test coverage thresholds. It guides the agent through reviewing a project's coverage configuration, checking that minimum thresholds are set and enforced in CI/CD, and flagging gaps where the rule is only documented but not automatically verified. It covers setting global thresholds, applying stricter ones to critical code, and excluding generated files.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent that can load skills, and a project with a testing framework such as Jest or Vitest.
Then ask your AI: use the Maintain test coverage thresholds skill
What your AI can do with it
- Review a project's test coverage configuration for minimum thresholds
- Check that coverage thresholds are enforced in CI/CD, not just documented
- Flag gaps where coverage failures do not block regressions
- Explain how to set up thresholds and appropriate levels for different code types
- Review tests and CI workflows related to coverage enforcement
- Point to framework-specific guidance in references/rule.md
Getting started
- Have an agent that can load skills, and a project with a testing framework such as Jest or Vitest.
- Add the test-coverage skill to the agent's available skills.
- Ask the agent to review the project's test coverage configuration and CI checks.
- Apply the agent's suggested fixes by configuring thresholds in the testing framework and adding coverage checks to CI/CD.
- Consult references/rule.md for full implementation details and code examples.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/test-coverage/SKILL.md and read by ahel’s review.
Coverage thresholds prevent code quality from degrading over time by failing builds when test coverage drops below safe levels.
Quick Reference
- Set global thresholds: 70% branches, 80% lines/functions/statements
- Apply stricter thresholds (90%+) to critical utility code
- Exclude generated code, type definitions, and config files
- Focus on meaningful coverage—test behavior, not just lines
Check
Review this project's test coverage configuration to ensure minimum thresholds are set and enforced in CI/CD.
Fix
Configure coverage thresholds in Jest, Vitest, or your testing framework, and add coverage checks to CI/CD.
Explain
Explain how to set up test coverage thresholds and what coverage levels are appropriate for different types of code.
Code Review
Review tests, CI workflows, and enforcement points related to Maintain test coverage thresholds. Flag exact gaps where the rule is not automatically verified or where failures do not block regressions.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/testing/test-coverage
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- What coverage thresholds are recommended?
- Global thresholds of 70% branches and 80% lines, functions, and statements, with stricter thresholds of 90% or more for critical utility code.
- Should any files be excluded from coverage?
- Yes. Exclude generated code, type definitions, and config files, and focus on meaningful coverage that tests behavior rather than just lines.
Advanced
- Item type
- skill
- Key
test-coverage-thedaviddias- Source
- github.com/thedaviddias/front-end-checklist