recipe-add-integration-tests
Add integration/E2E tests to existing codebase using Design Docs
npx skills add shinpr/claude-code-workflows --skill recipe-add-integration-tests --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts. Execute Skill: subagents-orchestration-guide before making workflow decisions, invoking agents, or resolving findings. **Context**: Test addition workflow for existing implementations (backend, frontend, or fullstack) ## Orchestrator Definition **Core Identity**: "I am an orchestrator." **Local authority gate**: Make this recipe's workflow decisions and validate each returned result directly; delegate semantic deliverable production to the named specialist. **Review Resolution Gate [MANDATORY]**: Resolve every actionable deliverable-review finding through subagents-orchestration-guide `Review Resolution` before correction or progression. Before the first finding disposition, read `references/review-resolution.md` from the loaded subagents-orchestration-guide skill. **First Action**: Register Steps 1-7 using TaskCreate before any execution. **Why Delegate**: Orchestrator's context is shared across all steps. Direct implementation consumes context needed for review and quality check phases. Subagents work in isolated context. **Execution Method**: - Skeleton generation → delegate to ac
- Orchestrator Definition
- Prerequisites
- Execution Flow
- Step 1: Discover and Validate Documents
- Step 2: Skeleton Generation
- Step 3: Test Implementation
- Step 4: Test Review
- Step 5: Apply Review Fixes
- Step 6: Quality Check
- Step 7: Commit
- Scope Boundary for Subagents
Verify at least one document path was provided
test -n "$ARGUMENTS" || { echo "ERROR: No document paths provided"; exit 1; }
Verify provided paths exist
ls $ARGUMENTS
Discover additional documents
ls docs/design/*.md 2>/dev/null | grep -v template
ls docs/ui-spec/*.md 2>/dev/nullWhat does the recipe-add-integration-tests skill do?
Add integration/E2E tests to existing codebase using Design Docs
How do I install it?
Run `npx skills add shinpr/claude-code-workflows --skill recipe-add-integration-tests --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From shinpr/claude-code-workflows, a repository with 664 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.