Fix spawn-issues to use correct subagent_type for each agent

- Issue worker: "general-purpose" → "issue-worker"
- Code reviewer: Added explicit subagent_type: "code-reviewer"
- PR fixer: Added explicit subagent_type: "pr-fixer"

Using the wrong agent type caused permission loops when spawning
background agents.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-10 16:13:09 +01:00
parent c9a72bf1d3
commit e1c19c12c3

View File

@@ -75,7 +75,7 @@ For each issue number, spawn a background issue-worker agent and track its task_
```
Task tool with:
- subagent_type: "general-purpose"
- subagent_type: "issue-worker"
- run_in_background: true
- prompt: <issue-worker prompt below>
```
@@ -184,6 +184,14 @@ implementing → (worker done) → reviewing → (approved) → DONE
When spawning reviewers, pass the PR number AND branch name from the issue worker result.
Each reviewer/fixer uses its own worktree for isolation - this prevents parallel agents from interfering with each other.
**Code Reviewer:**
```
Task tool with:
- subagent_type: "code-reviewer"
- run_in_background: true
- prompt: <code-reviewer prompt below>
```
**Code Reviewer Prompt:**
```
You are a code-reviewer agent. Review PR #<PR_NUMBER> autonomously.
@@ -241,10 +249,18 @@ All done!
3 PRs created and approved
```
## PR Fixer Prompt
## PR Fixer
When spawning pr-fixer for a PR that needs work:
```
Task tool with:
- subagent_type: "pr-fixer"
- run_in_background: true
- prompt: <pr-fixer prompt below>
```
**PR Fixer Prompt:**
```
You are a pr-fixer agent. Address review feedback on PR #<NUMBER>.