Writes plain-English integration test specs with verifiable steps and expectations, then runs each one through a subagent that reports pass or fail with logs.
Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror
Install Automate Integration Test
$ npx skills add openshift/oc-mirror --skill automate-integration-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift/oc-mirror automate-integration-test --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/automate-integration-test .claude/skills/automate-integration-test && 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 "automate-integration-test" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/automate-integration-test into .claude/skills/automate-integration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-integration-test", 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/automate-integration-testType 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 automate-integration-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift/oc-mirror automate-integration-test --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/automate-integration-test .agents/skills/automate-integration-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "automate-integration-test" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/automate-integration-test into .agents/skills/automate-integration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-integration-test", 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 automate-integration-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift/oc-mirror automate-integration-test --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/automate-integration-test .cursor/skills/automate-integration-test && 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 "automate-integration-test" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/automate-integration-test into .cursor/skills/automate-integration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-integration-test", 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/automate-integration-test--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 automate-integration-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift/oc-mirror automate-integration-test --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/automate-integration-test .gemini/skills/automate-integration-test && 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 "automate-integration-test" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/automate-integration-test into .gemini/skills/automate-integration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-integration-test", 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 automate-integration-testInstalls 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 automate-integration-test -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/automate-integration-test .github/skills/automate-integration-test && 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 "automate-integration-test" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/automate-integration-test into .github/skills/automate-integration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-integration-test", 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 automate-integration-test -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 automate-integration-test --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/automate-integration-test .opencode/skills/automate-integration-test && 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 "automate-integration-test" agent skill from https://github.com/openshift/oc-mirror/tree/main/.agents/skills/automate-integration-test into .opencode/skills/automate-integration-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automate-integration-test", 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
automate-integration-test- GitHub stars
- 124
- Token cost
- ~862 tokens
- SKILL.md length
- 435 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror
- Works in 10 steps: Read project conventions → Clarify if needed → Check for duplicate or superfluous… → …
- Tasks that involve Integration testing
- SKILL.md covers Test Images and Step-by-step process
- Calls go
What it does
Automate Integration Test is an agent skill from openshift/oc-mirror. Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror
Its SKILL.md is about 860 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 Integration testing and Test generation. 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 Integration testing
- Tasks that involve Test generation
Example prompts
- “/automate-integration-test”
Workflow steps
10 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:
go
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
Automate Integration Test loads about 862 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 435 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). 435 words, ~862 tokens.
Download SKILL.mdSave it as
.claude/skills/automate-integration-test/SKILL.md (or your agent's skills folder).- name
- automate-integration-test
- description
- Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror
- user-invocable
- true
Automate Manual Test Case to Go
Convert a manual test case description into a Ginkgo v2 integration test for the oc-mirror integration test suite.
Test Images
These are minimal images we generated and host ourselves to keep tests fast and self-contained, avoiding dependencies on external images that might change frequently.
- Catalog:
quay.io/oc-mirror/oc-mirror-dev:test-catalog-latest - Release:
quay.io/oc-mirror/release/test-release-index:v0.0.1 - Additional:
quay.io/openshifttest/hello-openshift@sha256:61b8f5...
Step-by-step process
1. Read project conventions
Read AGENTS.md at the project root for architecture, conventions, and pitfalls.
2. Clarify if needed
If the test case is ambiguous, ask before writing code:
- Which mirror mode? (
mirrorToMirror,mirrorToDisk+diskToMirror, or both) - Does it include a delete workflow (phase 1 + phase 2)?
- Is a new ISC or DISC YAML needed, or does an existing one suffice?
- Should the test go in an existing file or a new one?
3. Check for duplicate or superfluous coverage
Read existing test files to ensure the scenario isn't already covered. If it is, tell the user and suggest what would add value instead. Also consider if one of the existing tests could be extended to cover the scenario, without blurring the testing boundaries.
4. Discover available APIs
Read these files to learn the current patterns - do not guess or reinvent:
tests/integration/integration_suite_test.go- globals and lifecycletests/integration/helpers_test.go- assertion helpers- An existing test file matching the scenario type - to see calling conventions
Prefer existing helpers. If a new one is needed, follow the expect* naming pattern.
5. Analyze oc-mirror APIs if needed
If technical details are unclear:
- Check for a local copy at
./oc-mirror - Otherwise ask the user for a path or permission to clone from
github.com:openshift/oc-mirror.git
Show full SKILL.md (172 more words)Show less
6. Write the test
Follow the patterns from existing tests. Key rules:
- Match the structure of existing tests in the target file -
Describe,BeforeEach/AfterEach,It,Bysteps - Consider if the scenario covers all critical paths, and suggest new ones
- Implement meaningful assertions - avoid surface-level or redundant checks
- For error scenarios, assert on
result.ExitCodeandresult.Stderrcontent
7. Choose or create ISC/DISC configs
Check existing configs in tests/integration/testdata/imagesetconfigs/ first. Only create new ones if needed, using the same YAML structure and the test images listed in AGENTS.md.
8. Review the code
Before running, review the generated code for:
- Correctness: assertions actually verify the scenario, no false positives or dead steps
- Efficiency: no redundant operations, unnecessary variables, or repeated lookups
- Cleanliness: no superfluous comments, unused variables, or boilerplate that adds nothing - every line should earn its place
9. Run the tests
Ask for permission, then run.
go test -v ./tests/integration/ --ginkgo.focus "<test label>"10. Output
Provide the complete Go test code, any new YAML configs, and a one-line summary of where each file goes. Be concise - the user knows the project.
© 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/automate-integration-test of openshift/oc-mirror.
Open the folder on GitHubat commit 873d7db
Compare with similar skills
Automate Integration Test 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 |
|---|---|---|---|---|---|---|
| Automate Integration Test this skillopenshift/oc-mirror | 124 | — | ~862 | Automated safety check: Pass | Apache-2.0 | |
| Agent Integration Testingav/mi | 102 | — | ~908 | Automated safety check: Pass | None | |
| Write Frontend TestsElite588/AUTOGPT | 103 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| API Test Suite Builderalirezarezvani/claude-skills | 28k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Atmos Testscloudposse/atmos | 1.4k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Memstack Development Test Writercwinvestments/memstack | 423 | — | ~3.7k | Automated safety check: Pass | Proprietary |
Similar skills
Write Frontend Tests
Elite588/AUTOGPT
Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them.
API Test Suite Builder
alirezarezvani/claude-skills
A skill your agent uses when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.
Atmos Tests
cloudposse/atmos
Author Atmos smoke tests, post-deployment stack checks, and integration tests using type: test, HTTP assertions, shell or script/interpreter checks, require gates, parallel dependencies, matrix…
Memstack Development Test Writer
cwinvestments/memstack
A skill your agent uses when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with…
Frappe Testing Unit
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests.
More from openshift/oc-mirror
Check Test Coverage
openshift/oc-mirror
Analyze oc-mirror CLI feature coverage across integration and e2e tests, identifying untested features and gaps
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 Automate Integration Test
What does Automate Integration Test do?
Convert a manual test case description into a Ginkgo oc-v2 integration test for oc-mirror. Automate Integration Test is an agent skill from openshift/oc-mirror.
When should I use Automate Integration Test?
Automate Integration Test fits situations like: tasks that involve Integration testing; tasks that involve Test generation.
How do I install Automate Integration Test in Claude Code?
Run `npx skills add openshift/oc-mirror --skill automate-integration-test -a claude-code`. Or copy the skill folder (.agents/skills/automate-integration-test in openshift/oc-mirror) into .claude/skills/automate-integration-test in your project. Claude Code loads it when a task matches its description.
How do I install Automate Integration Test in Codex?
Run `npx skills add openshift/oc-mirror --skill automate-integration-test -a codex`. Or copy the skill folder (.agents/skills/automate-integration-test in openshift/oc-mirror) into .agents/skills/automate-integration-test in your project. Codex loads it when a task matches its description.
Can I use Automate Integration Test 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 automate-integration-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/automate-integration-test, .gemini/skills/automate-integration-test, .github/skills/automate-integration-test and .opencode/skills/automate-integration-test in your project.
What does Automate Integration Test need to run?
Going by SKILL.md and its folder, Automate Integration Test needs the command-line tools its instructions call (go).
Does Automate Integration Test 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 Automate Integration Test 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 Automate Integration Test use?
Automate Integration Test 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 Automate Integration Test use?
About 862 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 Automate Integration Test?
Skills that share tags, products or a category with Automate Integration Test: Agent Integration Testing (av/mi, 102 stars), Write Frontend Tests (Elite588/AUTOGPT, 103 stars), API Test Suite Builder (alirezarezvani/claude-skills, 28k stars) and Atmos Tests (cloudposse/atmos, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Automate Integration Test?
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.