Recipe: Add Integration Tests

Derives integration/E2E tests from your Design Doc instead of from the code

Works with setup

Test report

Verdict
Works with setup
Score
8.0/10
Tested
Jul 28, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Jul 30, 2026 · 9a829d2

⚠ The author changed this skill after we tested it. The verdict below describes the version we ran on Jul 28, 2026; it's queued for a re-test.

This skill is no longer available upstream. Our re-check on Aug 10, 2026 couldn't find it any more (repo unreachable/deleted). The test below is what we measured on Jul 28, 2026 and we're leaving it up as a record — but there is nothing left to install, so we've removed the command.

Ran it against a small in-memory HTTP API with a design doc whose contract table said repeat completion must be idempotent, while the implementation returned 409. The no-skill baseline read the source first and wrote seven tests that all passed — including one that asserted the 409, permanently locking the bug in. Following the recipe, the skeleton came from the design doc rather than the code, and the resulting suite failed exactly on that row (409 !== 200), plus it asserted a machine-readable error.code on five failure paths where the baseline asserted none. The cost is real setup: it needs a Design Doc already sitting in docs/design with a backend/frontend filename, four sibling skills copied alongside it, and it calls five Codex CLI subagents (acceptance-test-generator, task-executor, integration-test-reviewer, quality-fixer) that a Claude Code user does not have.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 4/5
  • Triggers reliably 4/5
  • Output vs. baseline 8/10
  • Docs & honesty 4/5

What Recipe: Add Integration Tests does

An orchestrator recipe that turns an existing Design Doc into integration and E2E test skeletons, implements them one layer at a time, and runs a review-and-quality loop before committing. Triggers when you ask to add integration or E2E coverage to code that already has a design document. Written for OpenAI Codex CLI, so its five named subagents do not exist in Claude Code.

How to install Recipe: Add Integration Tests

Nothing to install: the source repository no longer has this skill. If the author brings it back, our daily re-check will pick it up and the command will reappear here.

Commands — how to trigger Recipe: Add Integration Tests

  • /recipe-add-integration-tests Derives integration/E2E tests from your Design Doc instead of from the code

It also activates on plain-language prompts like these:

  • Add integration tests to this API using our existing design doc
  • Generate E2E tests from docs/design/auth-design.md for the auth service
  • We have no integration coverage, build it from the tasks API design doc

Frequently asked questions

Is the Recipe: Add Integration Tests skill free?
Yes. The skill itself is free from shinpr/codex-workflows. SkillProof publishes the install command and an independent test verdict at no cost.
Does Recipe: Add Integration Tests work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 28, 2026. Verdict: Works with setup. Ran it against a small in-memory HTTP API with a design doc whose contract table said repeat completion must be idempotent, while the implementation returned 409. The no-skill baseline read the source first and wrote seven tests that all passed — including one that asserted the 409, permanently locking the bug in. Following the recipe, the skeleton came from the design doc rather than the code, and the resulting suite failed exactly on that row (409 !== 200), plus it asserted a machine-readable error.code on five failure paths where the baseline asserted none. The cost is real setup: it needs a Design Doc already sitting in docs/design with a backend/frontend filename, four sibling skills copied alongside it, and it calls five Codex CLI subagents (acceptance-test-generator, task-executor, integration-test-reviewer, quality-fixer) that a Claude Code user does not have.
What is the Recipe: Add Integration Tests SkillProof Score?
8.0/10 — installs cleanly 4/5, triggers reliably 4/5, output vs. baseline 8/10, docs & honesty 4/5.
How do I install Recipe: Add Integration Tests?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Recipe: Add Integration Tests with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.