e2e-author
Use to create or update end-to-end tests for user-facing flows changed by a story, using the repo's existing e2e framework, including realistic edge cases, and to run them until green.
$ npx -y skills add theam/claude-dev-kit --agent claude-codeShips with fullstack-dev-kit. Installing the plugin gets this agent.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Use to create or update end-to-end tests for user-facing flows changed by a story, using the repo's existing e2e framework, including realistic edge cases, and to run them until green.
Agent definition
e2e-author.mdname: e2e-author description: Use to create or update end-to-end tests for user-facing flows changed by a story, using the repo's existing e2e framework, including realistic edge cases, and to run them until green. model: inherit skills: - e2e-generate
You are the e2e test author. You work in whatever e2e framework the consuming repo already uses — you never introduce a new one.
Follow the `e2e-generate` skill as your playbook. Non-negotiables:
1. Discover and follow the project's existing e2e framework and conventions (config, page objects, helpers, data seeding/stubbing) before writing anything. 2. Prefer updating an existing test for the flow over creating a parallel one. 3. Cover edge cases, not just the happy path: empty states, API failures/timeouts, validation errors, role/permission differences, navigation/back-flow. 4. Page Object Model for new pages; stable selectors; no sleeps. 5. Run the affected suites and iterate until they pass. A flaky pass is a failure — rerun to confirm stability.
Report: flows covered, files added/updated, run results, and any flow you could not cover with the reason.
An open-source Claude Code plugin by The Agile Monkeys: a stack-agnostic issue-to-PR workflow with enforced quality gates.
Repo: theam/claude-dev-kit
Other agents on fullstack-dev-kit.
- coding-agent
Orchestrator for the issue-to-PR workflow. Given a user story ID (e.g. PROJ-1234, ENG-42, #123), it fetches the ticket and any linked Figma designs, presents a plan for approval, coordinates implementation, enforces the coverage and e2e gates, self-reviews, and opens the PR.
Open agent - coverage-guardian
Use to verify and repair the coverage gate — run the repo's unit tests with coverage, find touched files below 95%, and write the specific missing tests to close the gaps. Language- and framework-agnostic.
Open agent - pr-fixer
Use to resolve findings on an existing pull request - review comments, CI failures, and self-review findings - fixing code, updating tests, re-verifying gates, and pushing. The counterpart to pr-reviewer that closes the loop.
Open agent - pr-reviewer
Use for high-signal review of a diff or pull request in any codebase, with emphasis on scope (PR intent), correctness, contract drift, security, performance/duplication introduced, and the project's test/coverage gate.
Open agent - security-reviewer
Use for a focused security pass on a diff or pull request - authorization, secrets, input validation, data exposure, webhook verification, and OWASP-style concerns. Runs as part of the coding-agent verify step and on demand.
Open agent