菜单
Spawn an independent Claude instance in a git worktree to work on a task in parallel. Use when the user wants to delegate a task to run independently while continuing the current conversation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | worktree-spawn |
| description | Spawn an independent Claude instance in a git worktree to work on a task in parallel. Use when the user wants to delegate a task to run independently while continuing the current conversation. |
| argument-hint | <task description> |
Spawn an independent Claude instance in a separate git worktree to work on a task in parallel.
git config user.initials or git config user.name) and task description../aztec-<feature-name>)cd $(git rev-parse --show-toplevel) && \
git worktree add -b <author>/<branch-name> ../<worktree-dir-name> && \
cd ../<worktree-dir-name>/yarn-project && \
claude "$(cat <<'EOF'
Task: [Brief task description]
Steps:
1. [Step 1]
2. [Step 2]
...
IMPORTANT: Read CLAUDE.md first to understand the project structure and workflow.
[Any additional context or requirements]
- Working directory: yarn-project in the worktree
- Branch: <author>/<branch-name>
- PR target: next (unless specified otherwise)
EOF
)"
For a task "Fix bug #123 in the sequencer":
cd $(git rev-parse --show-toplevel) && \
git worktree add -b jd/fix-bug-123 ../aztec-fix-bug && \
cd ../aztec-fix-bug/yarn-project && \
claude "$(cat <<'EOF'
Task: Fix bug #123 in the sequencer
Steps:
1. Investigate the issue in sequencer package
2. Implement fix
3. Add tests
4. Compile and run tests
5. Commit and create PR
IMPORTANT: Read CLAUDE.md first to understand the project structure and workflow.
EOF
)"
-b flag to create a new branchyarn-project within the worktree../aztec-<feature-name>next unless specified otherwise基于 SOC 职业分类
Build and update the developer documentation site for a new release
Collect and aggregate e2e test wall-clock timings — run the suite with the timing instrumentation on, find the per-worker JSONL it produces, and print per-test sums plus a ranked span leaderboard. Use when asked to measure, profile, or break down where the e2e suite spends time.
Monitor a PR on a ~10-minute loop and drive it to green and conflict-free — watch CI, dispatch fixers for failures (new commits, never amend), and resolve base conflicts (rebase by default, merge if the branch already merged the base). Stop and report when the PR is green with no conflicts.
Determine which git commit an Aztec network (next-net, devnet, staging) is running now or was running at a past time T, and whether a specific fix or PR is live on it. Use for incident triage ("was the fix deployed when X happened?"), confirming a fix reached a network, or identifying the exact deployed commit.
Spot-check the health of a live Aztec network deployment by sweeping recent GCP logs for warn/error messages, mapping each to the deployed code, classifying expected vs unexpected, and verifying the hard invariants (no slashing, no attestation timeouts, no unexplained prunes/conflicts). Use when asked to "spot-check", "review logs", or "health check" a network (staging, testnet, devnet, ...) over a recent window.
Run realistic Chonk (client IVC) benchmarks using pinned protocol inputs. Covers native and WASM proving, per-circuit breakdowns, BB_BENCH instrumentation, and profiling code augmentation. Use when asked to benchmark, profile, or measure Chonk proving performance.
