Menú
Abandon an active issue or release a stale issue claim so another agent can pick it up.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Use in repositories that track work with the agent-issues local issue workflow.
Claim exactly one issue, fix it, and create a pull request starting from a clean branch.
Prepare and open a pull request for the current branch after validating the full diff and running checks.
Push the current branch, open or update its PR, and loop through CI failures and review feedback until the PR is clean.
Like solve-issue, but skips plan confirmation and goes straight to implementation.
Basado en la clasificación ocupacional SOC
| name | abandon-issue |
| description | Abandon an active issue or release a stale issue claim so another agent can pick it up. |
Release the current worktree's issue claim. Use this when you determine an active issue isn't worth fixing, it is blocked on something you can't resolve, you need to bail out, or a stale claim is preventing new work.
Releasing a stale claim is always authorized and does not require user approval. A claim is stale when the prior work is demonstrably finished or no longer active, such as after its resolving PR was merged, or when the worktree is clean at the default branch with no open PR after completing that work.
Run the abandon helper:
issue-abandon
For abandoned active work, clean up the branch — reset back to the default branch so the worktree is ready for the next issue:
git checkout $(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name)
Skip branch cleanup when merely releasing a stale claim and the worktree is already clean and ready. Stale-claim recovery is claim-store bookkeeping; do not reset or switch an already-ready branch.
If you pushed a remote branch or created a draft PR, consider cleaning those up too (ask the user first).
Optionally restart /solve-issue to pick a different issue.