Menu
Verify SWEny provider credentials and connectivity. Run to diagnose configuration issues before running workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run SWEny E2E browser test workflows from .sweny/e2e/. Use when the user wants to execute end-to-end tests.
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 | check |
| description | Verify SWEny provider credentials and connectivity. Run to diagnose configuration issues before running workflows. |
| allowed-tools | Bash |
Verify that all configured provider credentials are valid and connectivity works. Tests each provider (Anthropic, Datadog, Sentry, Linear, GitHub, etc.) and reports status.
sweny check
Each provider shows one of:
If any provider shows fail, the user needs to update their .env or environment variables before running workflows.
This is a quick command (a few seconds). Run it before /sweny:triage or /sweny:implement if you suspect configuration issues.