Fix command substitution permission nag in submit-for-review

.agents/skills/submit-for-review/SKILL.md

@@ -35,7 +35,13 @@ If the current branch matches any of the above, **abort immediately** and say:
 First, move to the repository root so the command resolves against the correct Makefile / project config:
 
 ```
-cd "$(git rev-parse --show-toplevel)"
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above:
+
+```
+cd <repo-root>
 ```
 
 Then verify the make target exists before running it. Extract the target name from `make check` (e.g. `make check` → `check`) and run:
@@ -192,7 +198,13 @@ Wait for the review to complete and report its verdict.
 Before merging, verify the merge target exists. Move to the repo root, extract the target name from `make merge` (e.g. `make merge` → `merge`), and run:
 
 ```
-cd "$(git rev-parse --show-toplevel)" && make -n <target> 2>/dev/null
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above and check the target:
+
+```
+cd <repo-root> && make -n <target> 2>/dev/null
 ```
 
 If `make -n` exits non-zero, **stop** and say:
@@ -355,4 +367,4 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - `/submit-for-review` merges only to `dev` — never directly to `main`.
 - If `make merge` fails for any reason, report it and stop — do not attempt workarounds.
 - The follow-up issue offer in Step 9 runs only after a successful merge and only when the review produced non-blocking findings. Never prompt the user for follow-ups when the review blocked the merge — those findings should be fixed, not ticketed.
-<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: codex | hash: 2c94f1a3 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: codex | hash: 8a3a5c41 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

.claude/commands/submit-for-review.md

@@ -30,7 +30,13 @@ If the current branch matches any of the above, **abort immediately** and say:
 First, move to the repository root so the command resolves against the correct Makefile / project config:
 
 ```
-cd "$(git rev-parse --show-toplevel)"
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above:
+
+```
+cd <repo-root>
 ```
 
 Then verify the make target exists before running it. Extract the target name from `make check` (e.g. `make check` → `check`) and run:
@@ -187,7 +193,13 @@ Wait for the review to complete and report its verdict.
 Before merging, verify the merge target exists. Move to the repo root, extract the target name from `make merge` (e.g. `make merge` → `merge`), and run:
 
 ```
-cd "$(git rev-parse --show-toplevel)" && make -n <target> 2>/dev/null
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above and check the target:
+
+```
+cd <repo-root> && make -n <target> 2>/dev/null
 ```
 
 If `make -n` exits non-zero, **stop** and say:
@@ -350,4 +362,4 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - `/submit-for-review` merges only to `dev` — never directly to `main`.
 - If `make merge` fails for any reason, report it and stop — do not attempt workarounds.
 - The follow-up issue offer in Step 9 runs only after a successful merge and only when the review produced non-blocking findings. Never prompt the user for follow-ups when the review blocked the merge — those findings should be fixed, not ticketed.
-<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: claude | hash: 5ac043c0 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: claude | hash: cb5527b3 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

.cursor/rules/submit-for-review.mdc

@@ -36,7 +36,13 @@ If the current branch matches any of the above, **abort immediately** and say:
 First, move to the repository root so the command resolves against the correct Makefile / project config:
 
 ```
-cd "$(git rev-parse --show-toplevel)"
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above:
+
+```
+cd <repo-root>
 ```
 
 Then verify the make target exists before running it. Extract the target name from `make check` (e.g. `make check` → `check`) and run:
@@ -193,7 +199,13 @@ Wait for the review to complete and report its verdict.
 Before merging, verify the merge target exists. Move to the repo root, extract the target name from `make merge` (e.g. `make merge` → `merge`), and run:
 
 ```
-cd "$(git rev-parse --show-toplevel)" && make -n <target> 2>/dev/null
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above and check the target:
+
+```
+cd <repo-root> && make -n <target> 2>/dev/null
 ```
 
 If `make -n` exits non-zero, **stop** and say:
@@ -356,4 +368,4 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - `/submit-for-review` merges only to `dev` — never directly to `main`.
 - If `make merge` fails for any reason, report it and stop — do not attempt workarounds.
 - The follow-up issue offer in Step 9 runs only after a successful merge and only when the review produced non-blocking findings. Never prompt the user for follow-ups when the review blocked the merge — those findings should be fixed, not ticketed.
-<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: cursor | hash: 9ce06666 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: cursor | hash: cb8ce37e | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

.gemini/skills/submit-for-review/SKILL.md

@@ -35,7 +35,13 @@ If the current branch matches any of the above, **abort immediately** and say:
 First, move to the repository root so the command resolves against the correct Makefile / project config:
 
 ```
-cd "$(git rev-parse --show-toplevel)"
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above:
+
+```
+cd <repo-root>
 ```
 
 Then verify the make target exists before running it. Extract the target name from `make check` (e.g. `make check` → `check`) and run:
@@ -192,7 +198,13 @@ Wait for the review to complete and report its verdict.
 Before merging, verify the merge target exists. Move to the repo root, extract the target name from `make merge` (e.g. `make merge` → `merge`), and run:
 
 ```
-cd "$(git rev-parse --show-toplevel)" && make -n <target> 2>/dev/null
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above and check the target:
+
+```
+cd <repo-root> && make -n <target> 2>/dev/null
 ```
 
 If `make -n` exits non-zero, **stop** and say:
@@ -355,4 +367,4 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - `/submit-for-review` merges only to `dev` — never directly to `main`.
 - If `make merge` fails for any reason, report it and stop — do not attempt workarounds.
 - The follow-up issue offer in Step 9 runs only after a successful merge and only when the review produced non-blocking findings. Never prompt the user for follow-ups when the review blocked the merge — those findings should be fixed, not ticketed.
-<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: gemini | hash: a824146b | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: gemini | hash: 72b18480 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

skills/submit-for-review.md

@@ -38,7 +38,13 @@ If the current branch matches any of the above, **abort immediately** and say:
 First, move to the repository root so the command resolves against the correct Makefile / project config:
 
 ```
-cd "$(git rev-parse --show-toplevel)"
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above:
+
+```
+cd <repo-root>
 ```
 
 Then verify the make target exists before running it. Extract the target name from `{{CHECK_CMD}}` (e.g. `make check` → `check`) and run:
@@ -211,7 +217,13 @@ Wait for the review to complete and report its verdict.
 Before merging, verify the merge target exists. Move to the repo root, extract the target name from `{{MERGE_CMD}}` (e.g. `make merge` → `merge`), and run:
 
 ```
-cd "$(git rev-parse --show-toplevel)" && make -n <target> 2>/dev/null
+git rev-parse --show-toplevel
+```
+
+Then `cd` into the path returned above and check the target:
+
+```
+cd <repo-root> && make -n <target> 2>/dev/null
 ```
 
 If `make -n` exits non-zero, **stop** and say: