Official agent skill

Coverage

by pydantic in pydantic/monty

Fetch coverage diff from Codecov for the current branch or a specific PR.

OfficialMITAuto-check passedDevelopment

Install Coverage

skills CLI
$ npx skills add pydantic/monty --skill coverage -a claude-code

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

GitHub CLI
$ gh skill install pydantic/monty 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/pydantic/monty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/coverage .claude/skills/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
coverage
GitHub stars
8.6k
Token cost
~282 tokens
SKILL.md length
116 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Fetch coverage diff from Codecov for the current branch or a specific PR.

  • Development work in your project
  • SKILL.md covers Instructions, Output and Requirements
  • Calls uv

What it does

Coverage is an agent skill from pydantic/monty, published by the product's own GitHub organization. Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

Its SKILL.md is about 280 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 Development. The repository describes itself as: A minimal, secure Python interpreter written in Rust for use by AI. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/coverage”

What it can do on your machine

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

    • uv

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

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    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

Coverage loads about 282 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 116 words of instructions outside code blocks.

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

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 pydantic/monty at commit 5915273, republished under its MIT licence (© pydantic). 116 words, ~282 tokens.

Download SKILL.mdSave it as .claude/skills/coverage/SKILL.md (or your agent's skills folder).
name
coverage
description
Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

Coverage

Fetch line-by-line coverage information from Codecov for a GitHub pull request.

Instructions

Use this skill to check code coverage for your changes before merging.

Current branch (auto-detect PR)
bash
uv run scripts/codecov_diff.py

This auto-detects the org, repo, and PR number using the gh CLI based on the current branch.

Specific PR number
bash
uv run scripts/codecov_diff.py 123

Output

The script outputs:

  • PR title and state
  • HEAD coverage (overall coverage on the branch)
  • Patch coverage (coverage of changed lines only)
  • Coverage change (+/- percentage)
  • Per-file breakdown with:
    • Missed line count
    • Patch coverage percentage
    • Specific uncovered line numbers (as ranges like 45-48, 52, 60-65)
    • Partial coverage line numbers

Requirements

  • The gh CLI must be installed and authenticated for auto-detection
  • The PR must have Codecov coverage data uploaded

© pydantic, 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 .agents/skills/coverage of pydantic/monty.

Open the folder on GitHubat commit 5915273

Compare with similar skills

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.

Coverage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Coverage this skillpydantic/monty8.6k—~282Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 24 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from pydantic/monty

All 9 skills in this repo
  • Fix PR Comments

    pydantic/monty

    Official

    Read the review comments left by the known agent reviewers on the current PR, resolve and reply.

    8.6k GitHub stars~552 tokensUpdated yesterday
    Auto-check passed
  • Python Playground

    pydantic/monty

    Official

    Run and test Python code in a dedicated playground directory.

    8.6k GitHub stars~424 tokensUpdated yesterday
    Auto-check passed
  • Review General

    pydantic/monty

    Official

    Review the current branch against its merge base for bugs, CPython divergence, sandbox escapes, resource-limit escapes, performance regressions, verbose comments and missing ./limitations/ or docs/…

    8.6k GitHub stars~501 tokensUpdated yesterday
    Auto-check passed
  • Review Security

    pydantic/monty

    Official

    Security review of the current branch against its merge base — sandbox escapes, memory errors, panics and resource-limit bypasses.

    8.6k GitHub stars~852 tokensUpdated yesterday
    Auto-check passed
  • Writing Style

    pydantic/monty

    Official

    How to write prose that reads like human technical documentation rather than LLM output.

    8.6k GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • Review Usability

    pydantic/monty

    Official

    Check whether the common Python code an LLM would plausibly write still works on this branch, testing real cases in ./playground against CPython.

    8.6k GitHub stars~410 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Coverage

What does Coverage do?

Fetch coverage diff from Codecov for the current branch or a specific PR. Coverage is an agent skill from pydantic/monty, published by the product's own GitHub organization. Fetch coverage diff from Codecov for the current branch or a specific PR.

When should I use Coverage?

Coverage fits situations like: development work in your project.

How do I install Coverage in Claude Code?

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

How do I install Coverage in Codex?

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

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

What does Coverage need to run?

Going by SKILL.md and its folder, Coverage needs the command-line tools its instructions call (uv).

Does Coverage access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

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

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

About 282 tokens (SKILL.md is roughly 1.1k 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 Coverage?

Skills that share tags, products or a category with Coverage: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Coverage?

pydantic (a GitHub organization, an official publisher) maintains it in pydantic/monty, which has 8,581 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.

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