[Bug] Code-review plugin excessive permission prompts and unnecessary cd calls

[jkaster]

Bug Description
have you actually TRIED to use the new code-review plugin? It absolutely and totally sucks, prompting for permission hundreds of times, making unnecessary cd calls EVERY SINGLE TIME and requiring non-stop babysitting. It gets far, far worse if you try to run it from a Claude Code managed worktree. I'm shocked at how bad the UX currently is for an official Anthropic plugin.

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.73
• Feedback ID: 686d16e9-4788-4509-8027-27596f665571

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Claude always using cd command into current working directory in combination with Git commands, requiring approval for whitelisted commands #30832
2. [BUG] Permission prompt incorrectly triggers on cd instead of the actual command in compound bash statements #28240
3. Compound cd && git commands in worktrees should not require approval #30213

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[sunnypatell]

hey @jkaster, opened a PR that addresses the plugin-level side of this: #33397

two changes:

1. expanded allowed-tools to include git diff, git log, git blame, git show, git rev-parse, Read, Grep, Glob, and simplified the gh patterns to Bash(gh:*). agents were triggering permission prompts on every call because the tools they actually need weren't pre-approved
2. added an explicit "never prefix commands with cd" instruction to the agent assumptions block, which gets relayed to all sub-agents. this prevents the cd /path && command chaining that triggers the runtime's compound command security check

this won't fix the underlying runtime detection issue (#28240), but it should eliminate most of the permission prompt spam from the plugin itself.

[jkaster]

Hey thanks for the quick reply @sunnypatell! I'm looking forward to a more streamline code review agent. It sound some valid issues but it was just so painful to get through it I'll be sure to re-enable it when it's updated.