- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/shinpr/claude-code-workflows/tree/HEAD/dev-skills/skills/integration-e2e-testingFrom the publisher
Each test MUST include the following annotations:
AC: [Original acceptance criteria text]
Behavior: [Trigger] → [Process] → [Observable Result]
@lane: integration | fixture-e2e | service-integration-e2e
@dependency: none | [component names] | full-system
Selection evidence: [required claim, uncovered failure, and why cheaper existing proof is insufficient]
Use the project's comment syntax to wrap these annotations (e.g., // for C-family, # for Python/Ruby/Shell).
Selection evidence serves test selection and planning, so the implementing task removes it when it makes the test executable.
When verification points need explicit enumeration:
Verification items:
- [Item 1]
- [Item 2]
*.int.test.* or *.integration.test.**.fixture.e2e.test.* (or organize under tests/e2e/fixture/)*.service.e2e.test.* (or organize under tests/e2e/service/)The test runner or framework in the project determines the appropriate file extension. Repos that already use a single *.e2e.test.* convention may keep it as long as each file declares @lane: in its header — the lane annotation is the source of truth for routing.
When multiple routes reach the same mutation, compare validation, classification, resource bounds, and read/parse/mutation/reporting order. A difference becomes a proof obligation when it can violate an authoritative contract or expose a material bypass in the changed boundary. Reuse existing proof or add the smallest test that detects that failure.
Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when generating or consuming test skeletons or reviewing shared mutation routes.
---name: integration-e2e-testingdescription: Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use…---# dev-skills/skills/integration-e2e-testing/SKILL.mdFAQ
Download dev-skills/skills/integration-e2e-testing/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/shinpr/claude-code-workflows.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.