/run-e2e
Run end-to-end tests against the application using Playwright or Cypress.
$ npx -y skills add rohitg00/awesome-claude-code-toolkit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/run-e2e
Context preview
What this command does when you run it.
Run end-to-end tests against the application using Playwright or Cypress.
Command definition
run-e2e.md/run-e2e - Execute End-to-End Tests
Run end-to-end tests against the application using Playwright or Cypress.
Steps
1. Detect the e2e framework in use (Playwright, Cypress, or Selenium) by checking package.json and config files 2. Verify the test configuration file exists (playwright.config.ts, cypress.config.js, etc.) 3. Check if the application server is running; if not, identify the start command 4. List all e2e test files matching the pattern `**/*.e2e.{ts,js}` or `**/*.spec.{ts,js}` in the e2e/test directory 5. If a specific test file or pattern is provided, filter to those tests only 6. Run the test suite with verbose output and capture results 7. Parse test output for pass/fail counts and timing information 8. For any failing tests, extract the error message, screenshot path, and stack trace 9. Present a summary table: total tests, passed, failed, skipped, duration 10. If failures exist, suggest fixes based on error patterns (timeout, selector, assertion)
Rules
- Always run tests in headless mode unless the user explicitly requests headed mode
- Set a default timeout of 30 seconds per test unless configured otherwise
- Capture screenshots on failure automatically
- Do not modify test files without explicit permission
- Report flaky tests if a test passes on retry but failed initially
- Ensure the base URL matches the running application port
- Clean up any test artifacts older than 7 days
Read more
/run-e2e - Execute End-to-End Tests
Run end-to-end tests against the application using Playwright or Cypress.
Steps
1. Detect the e2e framework in use (Playwright, Cypress, or Selenium) by checking package.json and config files 2. Verify the test configuration file exists (playwright.config.ts, cypress.config.js, etc.) 3. Check if the application server is running; if not, identify the start command 4. List all e2e test files matching the pattern `**/*.e2e.{ts,js}` or `**/*.spec.{ts,js}` in the e2e/test directory 5. If a specific test file or pattern is provided, filter to those tests only 6. Run the test suite with verbose output and capture results 7. Parse test output for pass/fail counts and timing information 8. For any failing tests, extract the error message, screenshot path, and stack trace 9. Present a summary table: total tests, passed, failed, skipped, duration 10. If failures exist, suggest fixes based on error patterns (timeout, selector, assertion)
Rules
- Always run tests in headless mode unless the user explicitly requests headed mode
- Set a default timeout of 30 seconds per test unless configured otherwise
- Capture screenshots on failure automatically
- Do not modify test files without explicit permission
- Report flaky tests if a test passes on retry but failed initially
- Ensure the base URL matches the running application port
- Clean up any test artifacts older than 7 days
The most comprehensive toolkit for Claude Code -- 135 agents, 35 curated skills (+400,000 via SkillKit), 42 commands, 176+ plugins, 20 hooks, 15 rules, 7 templates, 15 MCP configs, 26 companion apps, 53 ecosystem entries, and more.
Repo: rohitg00/awesome-claude-code-toolkit
Other commands on rohitg00-claude-code-toolkit.
- /adr
Write an Architecture Decision Record documenting a significant technical decision.
Open command - /design-review
Conduct a structured design review of a module, feature, or system component.
Open command - /diagram
Generate Mermaid diagrams from codebase analysis or description.
Open command - /migrate
Plan and execute a framework or library migration incrementally.
Open command - /plan
Create a structured implementation plan for the requested feature or change.
Open command - /refactor
Perform a systematic refactoring of the specified code area.
Open command

