Agent skill

Code Coverage

by s3s-project in s3s-project/s3s

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

Apache-2.0Auto-check passedTesting & QA

Install Code Coverage

skills CLI
$ npx skills add s3s-project/s3s --skill code-coverage -a claude-code

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

GitHub CLI
$ gh skill install s3s-project/s3s code-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/s3s-project/s3s.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-coverage .claude/skills/code-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
code-coverage
GitHub stars
311
Token cost
~789 tokens
SKILL.md length
408 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Adding tests for generated code
  • SKILL.md covers Measure, Which number counts, Where tests for generated code… and Where tests for hand-written…, plus 1 more section
  • Calls cargo and just
  • Asked how much of s3s is covered

What it does

Code Coverage is an agent skill from s3s-project/s3s. Measure and grow the line coverage of the s3s crate. Use when adding tests for generated code, when asked how much of s3s is covered, or when a coverage number, goal or regression is discussed.

Its SKILL.md is about 790 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 licence is Apache-2.0.

When your agent uses it

  • Adding tests for generated code
  • Asked how much of s3s is covered
  • A coverage number
  • Regression is discussed

Example prompts

  • “/code-coverage”

What it can do on your machine

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

    • cargo
    • just

    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):

    • github.com

    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

Code Coverage loads about 789 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 408 words of instructions outside code blocks.

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

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 s3s-project/s3s at commit 1e1c52e, republished under its Apache-2.0 licence (© s3s-project). 408 words, ~789 tokens.

Download SKILL.mdSave it as .claude/skills/code-coverage/SKILL.md (or your agent's skills folder).
name
code-coverage
description
Measure and grow the line coverage of the s3s crate. Use when adding tests for generated code, when asked how much of s3s is covered, or when a coverage number, goal or regression is discussed.
license
Apache-2.0

Code coverage

The s3s crate is measured with cargo-llvm-cov. The goal for the crate is 90% line coverage.

Measure

sh
cargo llvm-cov -p s3s --all-features --no-fail-fast --json --summary-only --output-path target/coverage-s3s.json
cargo run -p xtask -- coverage target/coverage-s3s.json

xtask coverage prints one row per package plus a TOTAL row, and aggregates the per-file counters of the JSON export. --fail-under-lines 90 turns the same command into a gate; no CI job fails on coverage today, so a threshold is only enforced where it is passed explicitly.

Which number counts

  • The JSON summary is the reference: the line metric it prints is the one --fail-under-lines enforces.
  • --lcov and the text report count lines slightly differently and print a higher percentage for the same profile. Name the source of a number, and compare like with like.
  • The branches column stays at 0% unless the profile is built with --branch, which needs nightly.
  • cargo-llvm-cov ignores tests/ directories by default, so test bodies never enter the denominator. Keep it that way: tests belong in crates/s3s/tests/, not next to the code they exercise.

Where tests for generated code live

In crates/s3s/tests/generated/: a single integration-test binary, auto-discovered from tests/generated/main.rs, whose files are written by just codegen from the Smithy models (codegen/src/v1/gen_tests/).

  • Extend the generator instead of editing those files by hand: a model change then updates the code and its tests together, and the two cannot drift.
  • The module loader and the file set are fixed by the generator; add a family by adding an emitter module, not by dropping a file into the directory.
  • Emitters receive the base model and the MinIO model. Mirror the #[cfg(feature = "minio")] gates of the merged generated.rs, including the two branches of a type that the MinIO patch rewrites.
  • Assertions must be falsifiable: compare whole values or exact strings rather than is_empty()-style checks, and prove each family with a red control — inject an error into the production side and watch the matching case fail.
Show full SKILL.md (104 more words)Show less

Where tests for hand-written code live

Next to the existing integration tests in crates/s3s/tests/*.rs.

Growing the number

  • Start from the biggest gaps. xtask coverage gives the per-package rows; read data[0].files of the export, or cargo llvm-cov report, for the per-file ones.
  • Do not modify production code only to make a line coverable. Private items, defensive branches, branches decided by a cfg! constant and LLVM line-mapping artifacts are recorded as unreachable instead.
  • Attempt a cheaper input before writing a line off as unreachable: the closing brace of a skipped if let is covered by feeding the empty value, and a required field by omitting it.

© s3s-project, Apache-2.0. 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/code-coverage of s3s-project/s3s.

Open the folder on GitHubat commit 1e1c52e

Compare with similar skills

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

Code Coverage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Coverage this skills3s-project/s3s311—~789Automated safety check: PassApache-2.0
Requirementsrizsotto/Bear6.5k—~2kAutomated safety check: PassGPL-3.0
Crap Analysisardalis/RiverBooks1342 repos~3.4kAutomated safety check: PassNone
Project Statusbactopia/bactopia522—~787Automated safety check: PassMIT
Check Coverageldayton/Dippy243—~403Automated 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 today
    Testing & QAAuto-check passed
  • Crap Analysis

    ardalis/RiverBooks

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

    134 GitHub starsUsed in 2 repos~3.4k tokens
    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
  • Check Coverage

    ldayton/Dippy

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

    243 GitHub stars~403 tokensUpdated 3 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 s3s-project/s3s

All 10 skills in this repo
  • Gh Stack

    s3s-project/s3s

    Work with stacked pull requests in this repository using gh stack.

    311 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Code Review

    s3s-project/s3s

    Review a pull request or a proposed change to this repository.

    311 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Codegen

    s3s-project/s3s

    Change generated code in this repository. An agent skill from s3s-project/s3s.

    311 GitHub stars~726 tokensUpdated today
    Auto-check passed
  • Fuzz Testing

    s3s-project/s3s

    Add, run or schedule a fuzz target in this repository. An agent skill from s3s-project/s3s.

    311 GitHub stars~838 tokensUpdated today
    Auto-check passed
  • Mutation Testing

    s3s-project/s3s

    Run or triage the mutation sweep in this repository. An agent skill from s3s-project/s3s.

    311 GitHub stars~917 tokensUpdated today
    Auto-check passed
  • Pull Request

    s3s-project/s3s

    Prepare a change for this repository as a pull request. An agent skill from s3s-project/s3s.

    311 GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Code Coverage

What does Code Coverage do?

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

When should I use Code Coverage?

Code Coverage fits situations like: adding tests for generated code; asked how much of s3s is covered; A coverage number; regression is discussed.

How do I install Code Coverage in Claude Code?

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

How do I install Code Coverage in Codex?

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

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

What does Code Coverage need to run?

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

Does Code Coverage access the network?

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

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

Code Coverage is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Coverage use?

About 789 tokens (SKILL.md is roughly 3.2k 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 Code Coverage?

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

Who maintains Code Coverage?

s3s-project (a GitHub organization) maintains it in s3s-project/s3s, which has 311 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.

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