| name | issue-worker |
| description | Spawn a Claude worker to handle a GitHub issue. Fetches issue details, creates a feature branch, and works autonomously. Use when you want to delegate an issue to a worker. |
| allowed-tools | Bash, Read, Write, Edit, Glob, Grep |
Issue Worker Skill
Spawn a Claude worker to handle a GitHub issue.
Usage
/issue-worker <issue-number>
Examples
/issue-worker 42
/issue-worker 123
Instructions
When the user invokes /issue-worker, follow these steps:
1. Fetch Issue Details
gh issue view <issue-number> --json number,title,body,labels,comments
2. Generate Branch Name
Create a descriptive branch name from the issue:
- Format:
feat/issue-<number>-<short-description>
- Example: Issue #42 "Add retry logic" →
feat/issue-42-add-retry-logic
For bug issues, use fix/ prefix instead of feat/.
3. Create Worktree
BRANCH="feat/issue-<number>-<slug>"
WORKTREE_PATH="../artemis-issue-<number>"
git worktree add "$WORKTREE_PATH" -b "$BRANCH"
4. Build Task Prompt
Construct a comprehensive prompt for the worker:
You are working on GitHub Issue #<number>: <title>
## Issue Description
<body>
## Labels
<labels>
## Comments
<comments if any>
## Your Task
1. Understand the issue requirements
2. Implement the necessary changes
3. Write tests if applicable
4. Commit your changes with message referencing the issue (e.g., "feat: add retry logic (fixes #42)")
## Guidelines
- Follow existing code patterns in the repository
- Keep changes focused on the issue scope
- Add comments only where logic isn't self-evident
5. Spawn Worker
cd "$WORKTREE_PATH" && claude --print --dangerously-skip-permissions "$PROMPT"
6. Report Results
After completion:
- Show worker output summary
- Show commits made:
git log $BRANCH --oneline -5
- Show files changed:
git diff main...$BRANCH --stat
- Offer next steps:
- Create PR:
gh pr create --base main --head $BRANCH
- Review changes first
- Continue working on it
- Clean up if failed
7. Track Worker
Add to .claude/workers.json:
{
"type": "issue",
"issue": 42,
"branch": "feat/issue-42-add-retry-logic",
"worktree": "../artemis-issue-42",
"created": "2024-01-15T10:30:00Z",
"status": "completed"
}
Workflow Integration
After worker completes successfully, suggest:
gh pr create --title "feat: <issue title>" --body "Closes #<issue-number>"
This ensures the issue auto-closes when PR merges.
