skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
shinpr/claude-code-workflows83 installs

integration-e2e-testing

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.

How do I install this agent skill?

npx skills add https://github.com/shinpr/claude-code-workflows --skill integration-e2e-testing
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill establishes a framework for designing and evaluating integration and E2E tests based on external requirements documents. It is vulnerable to indirect prompt injection because it processes untrusted inputs such as Design Docs and PRDs to generate output, although it does not contain any direct malicious code.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1/1 file flagged

What does this agent skill do?

Integration and E2E Skeleton Contracts

Test Lanes

LaneObservable boundaryDependencies
integrationInteractions within a process, including framework-rendered UI and module/API handlersReal participating components; mock only outside the claimed boundary
fixture-e2eActual UI behavior in a real browser with deterministic fixturesFixtures may replace dependencies outside the claimed boundary
service-integration-e2eOutcome depends on actual cross-service interaction or persistenceRequired local services and stores are real; stubs only outside that proof boundary

Test Skeleton Specification

Required Comment Patterns

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).

Verification Items (Optional)

When verification points need explicit enumeration:

Verification items:
- [Item 1]
- [Item 2]

Test File Naming Convention

  • Integration tests: *.int.test.* or *.integration.test.*
  • fixture-e2e tests: *.fixture.e2e.test.* (or organize under tests/e2e/fixture/)
  • service-integration-e2e tests: *.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.

Route Parity for Shared Mutations

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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/shinpr/claude-code-workflows/integration-e2e-testing">View integration-e2e-testing on skillZs</a>