diff --git a/.agents/skills/submit-for-review/SKILL.md b/.agents/skills/submit-for-review/SKILL.md
index b004d8e..4bb8b8c 100644
--- a/.agents/skills/submit-for-review/SKILL.md
+++ b/.agents/skills/submit-for-review/SKILL.md
@@ -228,8 +228,8 @@ Accept: comma-separated numbers, `all`, or `none`/`skip`/empty. If the input is
 ```
 gh issue create \
   --title "<finding text with [WARNING]/[NOTE]/[CRITICAL] prefix stripped, trimmed to a standalone sentence>" \
-  --body-file - \
-  [--label "<pool-selected labels>"] <<'EOF'
+  [--label "<pool-selected labels>"] \
+  --body-file - <<'EOF'
 Follow-up from PR #<merged-pr-number> — auto-proposed from the code review.
 
 **Finding:** <full finding text, prefix included>
@@ -261,4 +261,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.sh | skill: submit-for-review | adapter: codex | hash: 61513e5d | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: submit-for-review | adapter: codex | hash: 7f9a2844 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
diff --git a/.claude/commands/submit-for-review.md b/.claude/commands/submit-for-review.md
index b7231f5..cf071a5 100644
--- a/.claude/commands/submit-for-review.md
+++ b/.claude/commands/submit-for-review.md
@@ -223,8 +223,8 @@ Accept: comma-separated numbers, `all`, or `none`/`skip`/empty. If the input is
 ```
 gh issue create \
   --title "<finding text with [WARNING]/[NOTE]/[CRITICAL] prefix stripped, trimmed to a standalone sentence>" \
-  --body-file - \
-  [--label "<pool-selected labels>"] <<'EOF'
+  [--label "<pool-selected labels>"] \
+  --body-file - <<'EOF'
 Follow-up from PR #<merged-pr-number> — auto-proposed from the code review.
 
 **Finding:** <full finding text, prefix included>
@@ -256,4 +256,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.sh | skill: submit-for-review | adapter: claude | hash: 2aa076dc | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: submit-for-review | adapter: claude | hash: 4845c4c2 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
diff --git a/.cursor/rules/submit-for-review.mdc b/.cursor/rules/submit-for-review.mdc
index b0d2f4b..7ac52cf 100644
--- a/.cursor/rules/submit-for-review.mdc
+++ b/.cursor/rules/submit-for-review.mdc
@@ -229,8 +229,8 @@ Accept: comma-separated numbers, `all`, or `none`/`skip`/empty. If the input is
 ```
 gh issue create \
   --title "<finding text with [WARNING]/[NOTE]/[CRITICAL] prefix stripped, trimmed to a standalone sentence>" \
-  --body-file - \
-  [--label "<pool-selected labels>"] <<'EOF'
+  [--label "<pool-selected labels>"] \
+  --body-file - <<'EOF'
 Follow-up from PR #<merged-pr-number> — auto-proposed from the code review.
 
 **Finding:** <full finding text, prefix included>
@@ -262,4 +262,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.sh | skill: submit-for-review | adapter: cursor | hash: 7fefc571 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: submit-for-review | adapter: cursor | hash: 3499993e | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
diff --git a/.gemini/skills/submit-for-review/SKILL.md b/.gemini/skills/submit-for-review/SKILL.md
index 32c0a9c..fa2e5d5 100644
--- a/.gemini/skills/submit-for-review/SKILL.md
+++ b/.gemini/skills/submit-for-review/SKILL.md
@@ -228,8 +228,8 @@ Accept: comma-separated numbers, `all`, or `none`/`skip`/empty. If the input is
 ```
 gh issue create \
   --title "<finding text with [WARNING]/[NOTE]/[CRITICAL] prefix stripped, trimmed to a standalone sentence>" \
-  --body-file - \
-  [--label "<pool-selected labels>"] <<'EOF'
+  [--label "<pool-selected labels>"] \
+  --body-file - <<'EOF'
 Follow-up from PR #<merged-pr-number> — auto-proposed from the code review.
 
 **Finding:** <full finding text, prefix included>
@@ -261,4 +261,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.sh | skill: submit-for-review | adapter: gemini | hash: c5b1249c | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: submit-for-review | adapter: gemini | hash: 56d02482 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
diff --git a/skills/submit-for-review.md b/skills/submit-for-review.md
index c746095..d598aec 100644
--- a/skills/submit-for-review.md
+++ b/skills/submit-for-review.md
@@ -268,8 +268,8 @@ Accept: comma-separated numbers, `all`, or `none`/`skip`/empty. If the input is
 ```
 gh issue create \
   --title "<finding text with [WARNING]/[NOTE]/[CRITICAL] prefix stripped, trimmed to a standalone sentence>" \
-  --body-file - \
-  [--label "<pool-selected labels>"] <<'EOF'
+  [--label "<pool-selected labels>"] \
+  --body-file - <<'EOF'
 Follow-up from PR #<merged-pr-number> — auto-proposed from the code review.
 
 **Finding:** <full finding text, prefix included>