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.
Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps
Install Check Test Coverage
$ npx skills add openshift/oc-mirror --skill check-test-coverage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift/oc-mirror check-test-coverage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/check-test-coverage .claude/skills/check-test-coverage && rm -rf skills-srcUse ~/.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/
Install the "check-test-coverage" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/check-test-coverage into .claude/skills/check-test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-test-coverage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift/oc-mirror/tree/main/.agents/skills/check-test-coverageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift/oc-mirror --skill check-test-coverage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift/oc-mirror check-test-coverage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/check-test-coverage .agents/skills/check-test-coverage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "check-test-coverage" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/check-test-coverage into .agents/skills/check-test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-test-coverage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift/oc-mirror --skill check-test-coverage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift/oc-mirror check-test-coverage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/check-test-coverage .cursor/skills/check-test-coverage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "check-test-coverage" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/check-test-coverage into .cursor/skills/check-test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-test-coverage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift/oc-mirror.git --path .agents/skills/check-test-coverage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift/oc-mirror --skill check-test-coverage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift/oc-mirror check-test-coverage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/check-test-coverage .gemini/skills/check-test-coverage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "check-test-coverage" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/check-test-coverage into .gemini/skills/check-test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-test-coverage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift/oc-mirror check-test-coverageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift/oc-mirror --skill check-test-coverage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/check-test-coverage .github/skills/check-test-coverage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "check-test-coverage" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/check-test-coverage into .github/skills/check-test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-test-coverage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift/oc-mirror --skill check-test-coverage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift/oc-mirror check-test-coverage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift/oc-mirror.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/check-test-coverage .opencode/skills/check-test-coverage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "check-test-coverage" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/check-test-coverage into .opencode/skills/check-test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-test-coverage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
check-test-coverage- GitHub stars
- 124
- Token cost
- ~853 tokens
- SKILL.md length
- 360 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps
- Works in 6 steps: Discover CLI features → Parse integration tests → Parse e2e tests → …
- Tasks that involve Test coverage
- Calls make
- Tasks that involve End-to-end testing
What it does
Check Test Coverage is an agent skill from openshift/oc-mirror. Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps
Its SKILL.md is about 850 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 and End-to-end testing. The repository describes itself as: Lifecycle manager for internet-disconnected OpenShift environments. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Test coverage
- Tasks that involve End-to-end testing
Example prompts
- “/check-test-coverage”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 873d7db. 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:
make
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 Test Coverage loads about 853 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 360 words of instructions outside code blocks.
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 openshift/oc-mirror at commit 873d7db, republished under its Apache-2.0 licence (© openshift). 360 words, ~853 tokens.
Download SKILL.mdSave it as
.claude/skills/check-test-coverage/SKILL.md (or your agent's skills folder).- name
- check-test-coverage
- description
- Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps
- user-invocable
- true
Check Test Coverage
Analyze which oc-mirror CLI features are tested at the integration and e2e levels, and which have gaps.
Step-by-step process
1. Discover CLI features
Run these commands to enumerate all subcommands and flags:
oc-mirror --v2 --help
oc-mirror --v2 delete --help
oc-mirror --v2 list operators --help
oc-mirror --v2 list releases --help
oc-mirror --v2 version --helpIf oc-mirror is not in PATH, build it first with make build and use ./bin/oc-mirror.
From the output, extract:
- Workflows: mirrorToMirror (m2m), mirrorToDisk (m2d), diskToMirror (d2m)
- Subcommands: delete, list operators, list releases, version
- Flags: every flag from each subcommand's help output (skip hidden/deprecated flags unless they appear in tests)
2. Parse integration tests
Read all *_test.go files in tests/integration/. For each file, extract:
- Ginkgo
Describe,Context, andItblock labels - Flags and workflows referenced in the test body (e.g.,
--dry-run,--delete-id,--from) - Helper function calls that exercise specific features
Build a map of feature -> test file + test label.
3. Parse e2e tests
Read test files in tests/e2e/test/e2e/ (primarily oc_mirror_v2.go). Extract:
- Test case descriptions and case IDs
- Workflows and flags exercised in each case
- Test data configs referenced from
tests/e2e/test/e2e/testdata/
4. Cross-reference and classify
For each CLI feature (subcommand, flag, workflow), classify coverage:
| Level | Meaning |
|---|---|
| Covered | Tested at integration and/or e2e level with meaningful assertions |
| Partially covered | Only happy path, or tested at only one level when both would be appropriate |
| Not covered | No test exercises this feature |
Consider a feature "partially covered" if:
- It's only tested in the happy path but has error handling worth verifying
- It's a flag that modifies behavior but is only tested implicitly (e.g., the flag is set but its effect isn't asserted)
Show full SKILL.md (108 more words)Show less
5. Produce the report
Present results in this format:
Summary table
| Feature / Flag | Integration | E2E | Status |
|----------------------|-------------|------|------------------|
| m2m workflow | m2m_test.go | 73359| Covered |
| --dry-run | dry_run_... | - | Partially covered|
| --secure-policy | - | - | Not covered |
| ... | | | |Priority gaps
List the top uncovered or partially covered features, ordered by importance:
- Features that affect data correctness (e.g., signature verification, archive integrity)
- Features that affect user-facing behavior (e.g., filtering, error codes)
- Features that are operational concerns (e.g., parallelism, profiling)
For each gap, recommend:
- Which test level is appropriate (integration vs. e2e)
- A one-line description of what the test should verify
6. Optional: compare with previous run
If a previous coverage report exists in the conversation history, highlight what changed: new tests added, features that moved from "not covered" to "covered", and any regressions.
© openshift, 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/check-test-coverage of openshift/oc-mirror.
Open the folder on GitHubat commit 873d7db
Compare with similar skills
Check 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Check Test Coverage this skillopenshift/oc-mirror | 124 | — | ~853 | Automated safety check: Pass | Apache-2.0 | |
| Atdd Mutateswingerman/engineer | 154 | — | ~2.7k | Automated safety check: Pass | MIT | |
| E2E Test ThinkerUniClipboard/UniClipboard | 1.9k | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| E2E Test Creatorletehaha/moneymatter | 160 | — | ~2.4k | Automated safety check: Warn | AGPL-3.0 | |
| Platform Dsar Policy Manageforcedotcom/sf-skills | 1.1k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Post Dev Testsd0xdev/sd0x-harness | 192 | — | ~1.8k | Automated safety check: Notes | MIT |
Similar skills
E2E Test Thinker
UniClipboard/UniClipboard
Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.
E2E Test Creator
letehaha/moneymatter
Creates backend e2e tests for new or existing endpoints. An agent skill from letehaha/moneymatter.
Platform Dsar Policy Manage
forcedotcom/sf-skills
Configure, run, and audit DsarPolicy Right-to-Portability exports end to end: author the data map over a subject's related records, resolve a request's subject (email/name/id) to a root-entity…
Post Dev Test
sd0xdev/sd0x-harness
Post-development test completion. An agent skill from sd0xdev/sd0x-harness.
Test Coverage
luongnv89/skills
Generate unit tests for untested branches and edge cases. An agent skill from luongnv89/skills.
More from openshift/oc-mirror
Automate Integration Test
openshift/oc-mirror
Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror
Migrate E2E To Integration
openshift/oc-mirror
Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns
Related
Categories
Questions about Check Test Coverage
What does Check Test Coverage do?
Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps. Check Test Coverage is an agent skill from openshift/oc-mirror.
When should I use Check Test Coverage?
Check Test Coverage fits situations like: tasks that involve Test coverage; tasks that involve End-to-end testing.
How do I install Check Test Coverage in Claude Code?
Run `npx skills add openshift/oc-mirror --skill check-test-coverage -a claude-code`. Or copy the skill folder (.agents/skills/check-test-coverage in openshift/oc-mirror) into .claude/skills/check-test-coverage in your project. Claude Code loads it when a task matches its description.
How do I install Check Test Coverage in Codex?
Run `npx skills add openshift/oc-mirror --skill check-test-coverage -a codex`. Or copy the skill folder (.agents/skills/check-test-coverage in openshift/oc-mirror) into .agents/skills/check-test-coverage in your project. Codex loads it when a task matches its description.
Can I use Check 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 openshift/oc-mirror --skill check-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/check-test-coverage, .gemini/skills/check-test-coverage, .github/skills/check-test-coverage and .opencode/skills/check-test-coverage in your project.
What does Check Test Coverage need to run?
Going by SKILL.md and its folder, Check Test Coverage needs the command-line tools its instructions call (make).
Does Check Test 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 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 Check Test Coverage use?
Check Test Coverage is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Check Test Coverage use?
About 853 tokens (SKILL.md is roughly 3.4k 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 Test Coverage?
Skills that share tags, products or a category with Check Test Coverage: Atdd Mutate (swingerman/engineer, 154 stars), E2E Test Thinker (UniClipboard/UniClipboard, 1.9k stars), E2E Test Creator (letehaha/moneymatter, 160 stars) and Platform Dsar Policy Manage (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Check Test Coverage?
openshift (a GitHub organization) maintains it in openshift/oc-mirror, which has 124 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: openshift/oc-mirror on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.