菜单
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 职业分类
Spawn a Claude worker in an isolated git worktree for parallel development. Use when you need to work on a task in isolation without affecting current work.
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.
Launch the Karkinos TUI to monitor worker progress in a new terminal window.
Bump the version number in pyproject.toml, plugin.json, and marketplace.json, then commit and tag.
Spawn a Claude worker to address PR feedback, fix CI failures, or continue work on a pull request. Use when a PR needs updates based on review comments or failing checks.
Spawn a Claude worker to address PR feedback, fix CI failures, or continue work on a pull request. Use when a PR needs updates based on review comments or failing checks.
| 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)")
5. Push your branch and create a PR
## 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 the worker completes successfully and has made commits:
# Push the branch to origin
git push -u origin "$BRANCH"
# Create PR linking to the issue
gh pr create --title "<issue title>" --body "$(cat <<'EOF'
## Summary
<brief description of changes>
Closes #<issue-number>
## Changes
<list of key changes made>
---
🤖 Generated by Claude worker
EOF
)"
# Enable auto-merge (will merge automatically when CI passes)
gh pr merge --auto --squash
After completion:
git log $BRANCH --oneline -5git diff main...$BRANCH --statAdd 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",
"pr": "<pr-url>"
}