Menu
Pick up an issue and implement a fix with SWEny. Use when the user has an issue ID or URL they want resolved.
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
| name | implement |
| description | Pick up an issue and implement a fix with SWEny. Use when the user has an issue ID or URL they want resolved. |
| disable-model-invocation | true |
| allowed-tools | Bash |
| context | fork |
| agent | sweny-workflow |
| argument-hint | <issue-id-or-url> |
Run the SWEny implement workflow. This fetches an issue from the configured tracker (GitHub Issues, Linear, Jira), analyzes the codebase, implements a fix, and opens a pull request.
Requires: An issue ID or URL as the first argument.
sweny implement $ARGUMENTS --stream
If the user did not provide an issue ID, ask them for one before running. Do not run without an issue ID — the CLI will fail.
For dry-run mode (analyze and plan without creating a PR):
sweny implement $ARGUMENTS --stream --dry-run
--dry-run — analyze and plan without creating a branch or PR--base-branch <branch> — base branch for the PR (default: main)--max-implement-turns <n> — max coding agent turns (default: 40)Verify SWEny provider credentials and connectivity. Run to diagnose configuration issues before running workflows.
Run SWEny E2E browser test workflows from .sweny/e2e/. Use when the user wants to execute end-to-end tests.
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.