Agent skill

Check Coverage

by ldayton in ldayton/Dippy

Ensure comprehensive test coverage for a CLI handler. An agent skill from ldayton/Dippy.

MITAuto-check passedTesting & QA

Install Check Coverage

skills CLI
$ npx skills add ldayton/Dippy --skill check-coverage -a claude-code

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

GitHub CLI
$ gh skill install ldayton/Dippy check-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/ldayton/Dippy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/check-coverage .claude/skills/check-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
check-coverage
GitHub stars
243
Token cost
~403 tokens
SKILL.md length
142 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Ensure comprehensive test coverage for a CLI handler. An agent skill from ldayton/Dippy.

  • Works in 6 steps: Gather Documentation → Explore Subcommands → Review Existing Tests → …
  • Adding a new command
  • SKILL.md covers 1. Gather Documentation, 2. Explore Subcommands, 3. Review Existing Tests and 4. Add Missing Tests, plus 2 more sections
  • Calls just

What it does

Check Coverage is an agent skill from ldayton/Dippy. Ensure comprehensive test coverage for a CLI handler. Use when adding a new command or auditing existing handler coverage.

Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test coverage. The repository describes itself as: 🐤 Less permission fatigue, more momentum. Dippy knows what’s safe to run and keeps Claude on track when plans change. The licence is MIT.

When your agent uses it

  • Adding a new command
  • Auditing existing handler coverage

Example prompts

  • “/check-coverage”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Gather Documentation
  2. Explore Subcommands
  3. Review Existing Tests
  4. Add Missing Tests
  5. Iterate Until Tests Pass
  6. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 2edad4a. 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

    Shell commands in SKILL.md call:

    • just

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

  • Network

    No URLs in SKILL.md.

    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

Check Coverage loads about 403 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 142 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~403

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 ldayton/Dippy at commit 2edad4a, republished under its MIT licence (© ldayton). 142 words, ~403 tokens.

Download SKILL.mdSave it as .claude/skills/check-coverage/SKILL.md (or your agent's skills folder).
name
check-coverage
description
Ensure comprehensive test coverage for a CLI handler. Use when adding a new command or auditing existing handler coverage.
argument-hint
<tool>
disable-model-invocation
true

Ensure the handler and tests for $ARGUMENTS provide comprehensive coverage.

1. Gather Documentation

Find documentation for the tool (need at least one source):

tldr:

ls ~/source/tldr/pages/*/$ARGUMENTS*.md
cat ~/source/tldr/pages/*/$ARGUMENTS.md

Local CLI:

$ARGUMENTS --help
man $ARGUMENTS

Stop if neither source exists.

2. Explore Subcommands

For tools with subcommands, recursively explore:

$ARGUMENTS <subcommand> --help
$ARGUMENTS help <subcommand>

Build a mental model of:

  • All subcommands and their actions
  • Which operations are read-only (safe) vs mutate state (unsafe)
  • Global flags that affect parsing
  • Edge cases

3. Review Existing Tests

Read tests/cli/test_$ARGUMENTS.py and check for:

  • Coverage of all subcommands
  • Both safe and unsafe variants of each action
  • Global flag handling
  • Edge cases from the docs

4. Add Missing Tests

Add aspirational test cases for anything missing. Follow existing format:

python
TESTS = [
    # --- Subcommand group ---
    ("$ARGUMENTS <subcommand> <safe-action>", True),
    ("$ARGUMENTS <subcommand> <unsafe-action>", False),
]

5. Iterate Until Tests Pass

just test

For each failure, determine if the test expectation is correct:

  • If yes, update src/dippy/cli/$ARGUMENTS.py
  • If no, fix the test

6. Verify

just check MUST pass before you're done.

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

Files

Just SKILL.md in .claude/skills/check-coverage of ldayton/Dippy.

Open the folder on GitHubat commit 2edad4a

Compare with similar skills

Check 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.

Check Coverage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Check Coverage this skillldayton/Dippy243—~403Automated safety check: PassMIT
Requirementsrizsotto/Bear6.5k—~2kAutomated safety check: PassGPL-3.0
Crap Analysisardalis/RiverBooks1352 repos~3.4kAutomated safety check: PassNone
Code Coverages3s-project/s3s311—~789Automated safety check: PassApache-2.0
Project Statusbactopia/bactopia522—~787Automated safety check: PassMIT
Guarding Destructive Operationskajisho5/ffmpeg-skill1.9k—~2.6kAutomated safety check: PassMIT

Similar skills

  • Requirements

    rizsotto/Bear

    Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…

    6.5k GitHub stars~2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Crap Analysis

    ardalis/RiverBooks

    Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code.

    135 GitHub starsUsed in 2 repos~3.4k tokens
    Testing & QAAuto-check passed
  • Code Coverage

    s3s-project/s3s

    Measure and grow the line coverage of the s3s crate. An agent skill from s3s-project/s3s.

    311 GitHub stars~789 tokensUpdated today
    Testing & QAAuto-check passed
  • Project Status

    bactopia/bactopia

    Show a live snapshot of the Bactopia project state — component counts, GroovyDoc coverage, nf-test coverage, and structural issues.

    522 GitHub stars~787 tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Guarding Destructive Operations

    kajisho5/ffmpeg-skill

    Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of…

    1.9k GitHub stars~2.6k tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • Atdd Mutate

    swingerman/engineer

    A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.

    154 GitHub stars~2.7k tokensUpdated 14 days ago
    Testing & QAAuto-check passed

More from ldayton/Dippy

  • Add Command

    ldayton/Dippy

    Add support for a new CLI command. An agent skill from ldayton/Dippy.

    243 GitHub stars~567 tokensUpdated 3 mo ago
    Auto-check passed
  • Debug

    ldayton/Dippy

    Debug incorrect Dippy approval or block behavior. An agent skill from ldayton/Dippy.

    243 GitHub stars~235 tokensUpdated 3 mo ago
    Auto-check passed
  • Verify Counts

    ldayton/Dippy

    Verify numerical claims in documentation are still accurate. An agent skill from ldayton/Dippy.

    243 GitHub stars~344 tokensUpdated 3 mo ago
    Auto-check passed
  • Release

    ldayton/Dippy

    Create a release PR with version bump and changelog. An agent skill from ldayton/Dippy.

    243 GitHub stars~323 tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about Check Coverage

What does Check Coverage do?

Ensure comprehensive test coverage for a CLI handler. An agent skill from ldayton/Dippy. Check Coverage is an agent skill from ldayton/Dippy. Ensure comprehensive test coverage for a CLI handler.

When should I use Check Coverage?

Check Coverage fits situations like: adding a new command; auditing existing handler coverage.

How do I install Check Coverage in Claude Code?

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

How do I install Check Coverage in Codex?

Run `npx skills add ldayton/Dippy --skill check-coverage -a codex`. Or copy the skill folder (.claude/skills/check-coverage in ldayton/Dippy) into .agents/skills/check-coverage in your project. Codex loads it when a task matches its description.

Can I use Check 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 ldayton/Dippy --skill check-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/check-coverage, .gemini/skills/check-coverage, .github/skills/check-coverage and .opencode/skills/check-coverage in your project.

What does Check Coverage need to run?

Going by SKILL.md and its folder, Check Coverage needs the command-line tools its instructions call (just). Our summary lists: Python 3.

Does Check Coverage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Check 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 Check Coverage use?

Check 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 Check Coverage use?

About 403 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.

What are the alternatives to Check Coverage?

Skills that share tags, products or a category with Check Coverage: Requirements (rizsotto/Bear, 6.5k stars), Crap Analysis (ardalis/RiverBooks, 135 stars), Code Coverage (s3s-project/s3s, 311 stars) and Project Status (bactopia/bactopia, 522 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Check Coverage?

ldayton (a GitHub user) maintains it in ldayton/Dippy, which has 243 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 12, 2026.

Source: ldayton/Dippy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.