Agent skill

Test Coverage

by thedaviddias in thedaviddias/Front-End-Checklist

A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Maintain test coverage thresholds.

MITAuto-check passedTesting & QA

Install Test Coverage

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill test-coverage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist test-coverage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/test-coverage .claude/skills/test-coverage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-coverage
GitHub stars
74k
Token cost
~407 tokens
SKILL.md length
156 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Maintain test coverage thresholds.

  • Reviewing CI coverage
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Automated checks

What it does

Test Coverage is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing CI coverage, automated checks, or test strategy related to Maintain test coverage thresholds. Focus on whether the rule is continuously verified, not just documented.

Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).

It sits in Testing & QA, covering Test coverage and Test strategy. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.

When your agent uses it

  • Reviewing CI coverage
  • Automated checks
  • Test strategy related to Maintain test coverage thresholds

Example prompts

  • “/test-coverage”

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • frontendchecklist.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Coverage loads about 407 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 156 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~407
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 156 words, ~407 tokens.

Download SKILL.mdSave it as .claude/skills/test-coverage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
test-coverage
description
Use when reviewing CI coverage, automated checks, or test strategy related to Maintain test coverage thresholds. Focus on whether the rule is continuously verified, not just documented.
metadata.category
testing
metadata.priority
medium
metadata.difficulty
beginner
metadata.estimatedTime
15
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/testing/test-coverage

Maintain test coverage thresholds

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/rules/testing/test-coverage

© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/test-coverage of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

Test Coverage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Coverage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Coverage this skillthedaviddias/Front-End-Checklist74k—~407Automated safety check: PassMIT
Designing TestsCloudAI-X/opencode-workflow275—~2.9kAutomated safety check: PassMIT
Go TestingGentleman-Programming/gentle-ai7.6k—~550Automated safety check: PassApache-2.0
Functional Verificationhdl-tools/digital-chip-design-agents213—~4.5kAutomated safety check: NotesMIT
Automated Test Planningtestdouble/han279—~6.7kAutomated safety check: PassMIT
QA LeadIbrahim-3d/orchestrator-supaconductor381—~2.5kAutomated safety check: PassAGPL-3.0

Similar skills

  • Designing Tests

    CloudAI-X/opencode-workflow

    Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.

    275 GitHub stars~2.9k tokensUpdated 9 mo ago
    Testing & QAAuto-check passed
  • Go Testing

    Gentleman-Programming/gentle-ai

    Trigger: Go tests, go test coverage, Bubbletea teatest, golden files.

    7.6k GitHub stars~550 tokensUpdated today
    Testing & QAAuto-check passed
  • Functional Verification

    hdl-tools/digital-chip-design-agents

    UVM-based functional verification — testbench architecture, test planning, directed and constrained-random stimulus, functional and code coverage closure, formal assist, and regression sign-off.

    213 GitHub stars~4.5k tokensUpdated 6 days ago
    Testing & QAAuto-check: notes
  • Produce a standalone test plan by analyzing code for test coverage gaps and edge cases.

    279 GitHub stars~6.7k tokensUpdated 8 days ago
    Testing & QAAuto-check passed
  • QA Lead

    Ibrahim-3d/orchestrator-supaconductor

    Quality assurance consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

    381 GitHub stars~2.5k tokensUpdated 11 days ago
    Testing & QAAuto-check passed
  • Manual Test Planning

    testdouble/han

    Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by…

    279 GitHub stars~2.9k tokensUpdated 8 days ago
    Testing & QAAuto-check passed

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo
  • Content Dates Audit

    thedaviddias/Front-End-Checklist

    Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

    74k GitHub stars~691 tokensUpdated 3 days ago
    Auto-check passed
  • FAQPage Schema Markup

    thedaviddias/Front-End-Checklist

    Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

    74k GitHub stars~774 tokensUpdated 3 days ago
    Auto-check passed
  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated 3 days ago
    Auto-check passed
  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated 3 days ago
    Auto-check passed
  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 3 days ago
    Auto-check passed
  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Test Coverage

What does Test Coverage do?

A skill your agent uses when reviewing CI coverage, automated checks, or test strategy related to Maintain test coverage thresholds. Test Coverage is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing CI coverage, automated checks, or test strategy related to Maintain test coverage thresholds.

When should I use Test Coverage?

Test Coverage fits situations like: reviewing CI coverage; automated checks; test strategy related to Maintain test coverage thresholds.

How do I install Test Coverage in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill test-coverage -a claude-code`. Or copy the skill folder (skills/test-coverage in thedaviddias/Front-End-Checklist) into .claude/skills/test-coverage in your project. Claude Code loads it when a task matches its description.

How do I install Test Coverage in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill test-coverage -a codex`. Or copy the skill folder (skills/test-coverage in thedaviddias/Front-End-Checklist) into .agents/skills/test-coverage in your project. Codex loads it when a task matches its description.

Can I use Test Coverage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill test-coverage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-coverage, .gemini/skills/test-coverage, .github/skills/test-coverage and .opencode/skills/test-coverage in your project.

What does Test Coverage need to run?

SKILL.md names no scripts, command-line tools or credentials: Test Coverage is instructions for the agent only.

Does Test Coverage access the network?

SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.

Is Test Coverage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Coverage use?

Test Coverage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Coverage use?

About 407 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 837 tokens, read only when the agent opens those files.

What are the alternatives to Test Coverage?

Skills that share tags, products or a category with Test Coverage: Designing Tests (CloudAI-X/opencode-workflow, 275 stars), Go Testing (Gentleman-Programming/gentle-ai, 7.6k stars), Functional Verification (hdl-tools/digital-chip-design-agents, 213 stars) and Automated Test Planning (testdouble/han, 279 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Coverage?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,412 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.