code-reviewer-subagent-no-bash-blocked-on-pr-difflisted

Code-review subagents are frequently provisioned WITHOUT a Bash tool, so they cannot run `gh pr diff`, `git diff`, or `git checkout` — and when you prompt them to "review PR #N, fetch the diff with gh pr diff" they return a BLOCKED report (no review performed), not findings. Use when: (1) dispatching feature-dev:code-reviewer / voltagent-* / Explore agents to review GitHub PRs or branches; (2) a review agent returns "I have no shell/gh/git tool" or "the PR sources are not in the working tree" or reviews `main` (which predates the PR) instead of the PR; (3) one reviewer in a parallel panel comes back BLOCKED while siblings succeeded. Fix: pre-generate per-base diffs to files + point the agent at materialized worktree paths, don't tell it to run gh/git.
wan-huiyan/agent-traffic-control · ★ 2 · Code & Development · score 79

Install: claude install-skill wan-huiyan/agent-traffic-control

# Code-reviewer subagents have no Bash — blocked when told to `gh pr diff` ## Problem You dispatch a review-panel subagent (e.g. `feature-dev:code-reviewer`) to review open GitHub PRs, with a prompt like "use `gh pr diff <N>` to get each PR's diff, then review." The agent returns a **BLOCKED report** — no findings — explaining it has no shell/`gh`/`git` tool and the PR source isn't in the working tree. Meanwhile a sibling reviewer in the same panel may succeed (if it happened to find a materialized worktree on disk). The blocked run is wasted compute and, worse, can masquerade as "clean" if you don't read it carefully. ## Context / Trigger Conditions - Dispatching `feature-dev:code-reviewer`, `voltagent-qa-sec:*`, `Explore`, or similar review/search agents against a **GitHub PR or a branch not checked out in the main working tree**. - The agent's report says any of: "No shell / `gh` / `git` tool is exposed", "The PR sources are not in the working tree", "WebFetch returns 404 (private repo)", or it reviewed files on the **current branch (often `main`, which predates the PR)** instead of the PR's changes. - In a parallel panel, **asymmetric outcomes** — some reviewers found the code, one came back blocked — because the successful ones discovered an existing worktree path and the blocked one looked in the main checkout. ## Root cause These agents' toolsets exclude `Bash`. For example `feature-dev:code-reviewer` has `Glob, Grep, LS, Read, NotebookRead, WebFetc