#57 Introduced a regression: Command contains $() command substitution

[sebastientaggart]

Using Claude the pattern $(git) triggers a constant permissions check with no option to save the approval:

⏺ Bash(cd "$(git rev-parse --show-toplevel)" && make -n check 2>/dev/null)
  ⎿  Running…

─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
 Bash command

   cd "$(git rev-parse --show-toplevel)" && make -n check 2>/dev/null
   Verify make check target exists

 Command contains $() command substitution

 Do you want to proceed?
 ❯ 1. Yes
   2. No

 Esc to cancel · Tab to amend · ctrl+e to explain

One of the philosophies of this project is to make these processes as reliably automatic as possible, and constant repetitive permission nags isn't consistent with that goal.

[sebastientaggart]

Resuming work. Replacing $(git rev-parse --show-toplevel) command substitution patterns in submit-for-review skill with two-step commands to avoid Claude Code permission prompts.

[sebastientaggart]

Resolution

The shell commands that triggered repetitive permission prompts have been rewritten to avoid the pattern that Claude Code flags. Agents will no longer be interrupted by unskippable approval dialogs when navigating to the project root during the submit-for-review workflow.

See #139 for full technical details.