What problem does it solve? Turning a GitHub issue into a reviewed pull request involves repetitive, error-prone bookkeeping: naming branches consistently, avoiding duplicate work on issues already covered by a PR, isolating changes in worktrees, and explaining to each issue reporter what the PR proposes. This Skill automates that entire lifecycle so every issue follows the same auditable path from open issue to open PR. ## Core Features & Use Cases - Structured branch naming: Encodes PR number, issue number, and review finding ID in every branch name (e.g., PR68-Fix-I60-F3-rust-ps-path), with grouped and stacked variants for multi-issue units. - Duplicate-work and deferral guards: Checks open PRs, branch names, and deferral labels before starting, so an issue is never worked twice and deliberately deferred issues are never touched. - Worktree isolation and teardown: Creates a dedicated git worktree per issue, verifies clean state before removal, and keeps the worktree with a printed reason whenever teardown preconditions fail. - Per-issue resolution comments: Posts a proposal-phrased comment on each issue explaining the diagnosis, what the PR changes for that issue specifically, and what is deliberately out of scope. - Batch and stacked-PR support: Processes every unaddressed open issue sequentially using issue-triage dispositions, and restacks stacked PRs after a parent merges using recorded parent head SHAs. - Use Case: A maintainer returns from vacation to 12 open issues and types "/work-issue all" to get an ordered triage plan, then one worktree, branch, PR, and resolution comment per issue without manual bookkeeping. ## Quick Start Ask the assistant to work issue 60 on its own worktree, push the branch, open a PR, and post a resolution comment on the issue.
