Menu
Run SWEny E2E browser test workflows from .sweny/e2e/. Use when the user wants to execute end-to-end tests.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Verify SWEny provider credentials and connectivity. Run to diagnose configuration issues before running workflows.
Pick up an issue and implement a fix with SWEny. Use when the user has an issue ID or URL they want resolved.
Create standard SWEny label set in your issue tracker (Linear or GitHub). Run after init to prepare your tracker for triage.
Run SWEny triage to investigate production alerts, create issues, and optionally implement fixes. Use when the user wants to analyze recent errors or alerts.
Render a SWEny workflow as a Mermaid diagram for visualization.
Edit an existing SWEny workflow using natural language instructions.
| name | e2e-run |
| description | Run SWEny E2E browser test workflows from .sweny/e2e/. Use when the user wants to execute end-to-end tests. |
| disable-model-invocation | true |
| allowed-tools | Bash |
| context | fork |
| agent | sweny-workflow |
| argument-hint | [file] [--timeout <ms>] |
Run agent-driven browser end-to-end tests. Executes workflow files from .sweny/e2e/.
Prerequisites: E2E workflows must exist in .sweny/e2e/. Run /sweny:e2e-init first if the directory is empty.
Run all E2E tests:
sweny e2e run
Run a specific test file:
sweny e2e run $ARGUMENTS
With a custom timeout (default is 15 minutes per workflow):
sweny e2e run --timeout 300000
e2e-{run_id} patterns is automatically cleaned up if a cleanup backend is configuredE2E_BASE_URL — override the base URL for testsE2E_EMAIL — override test email (default: e2e-{run_id}@yourapp.test)E2E_PASSWORD — override test password