메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| 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 |
Spawn a Claude worker to handle a GitHub issue.
/issue-worker <issue-number>
/issue-worker 42
/issue-worker 123
When the user invokes /issue-worker, follow these steps:
gh issue view <issue-number> --json number,title,body,labels,comments
Create a descriptive branch name from the issue:
feat/issue-<number>-<short-description>feat/issue-42-add-retry-logicFor bug issues, use fix/ prefix instead of feat/.
BRANCH="feat/issue-<number>-<slug>"
WORKTREE_PATH="../artemis-issue-<number>"
git worktree add "$WORKTREE_PATH" -b "$BRANCH"
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
cd "$WORKTREE_PATH" && claude --print --dangerously-skip-permissions "$PROMPT"
After completion:
git log $BRANCH --oneline -5git diff main...$BRANCH --statgh pr create --base main --head $BRANCHAdd 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"
}
After worker completes successfully, suggest:
# Create PR linking to issue
gh pr create --title "feat: <issue title>" --body "Closes #<issue-number>"
This ensures the issue auto-closes when PR merges.