- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add shinpr/claude-code-workflows --skill integration-e2e-testing -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/shinpr/claude-code-workflows/tree/HEAD/dev-workflows-frontend/skills/integration-e2e-testingDel publicador
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-workflows-frontend/skills/integration-e2e-testing/SKILL.mdPreguntas frecuentes
Descarga dev-workflows-frontend/skills/integration-e2e-testing/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/shinpr/claude-code-workflows.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.