From a5ca58d5fd502630fc0e9b5499a867ac50977d55 Mon Sep 17 00:00:00 2001 From: Sebastien Taggart Date: Thu, 9 Apr 2026 19:49:18 -0400 Subject: [PATCH] Place --body-file - adjacent to heredoc in gh issue create example for readability --- .agents/skills/submit-for-review/SKILL.md | 6 +++--- .claude/commands/submit-for-review.md | 6 +++--- .cursor/rules/submit-for-review.mdc | 6 +++--- .gemini/skills/submit-for-review/SKILL.md | 6 +++--- skills/submit-for-review.md | 4 ++-- 5 files changed, 14 insertions(+), 14 deletions(-) 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 "" \ - --body-file - \ - [--label ""] <<'EOF' + [--label ""] \ + --body-file - <<'EOF' Follow-up from PR # — auto-proposed from the code review. **Finding:** @@ -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. - + 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 "" \ - --body-file - \ - [--label ""] <<'EOF' + [--label ""] \ + --body-file - <<'EOF' Follow-up from PR # — auto-proposed from the code review. **Finding:** @@ -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. - + 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 "" \ - --body-file - \ - [--label ""] <<'EOF' + [--label ""] \ + --body-file - <<'EOF' Follow-up from PR # — auto-proposed from the code review. **Finding:** @@ -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. - + 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 "" \ - --body-file - \ - [--label ""] <<'EOF' + [--label ""] \ + --body-file - <<'EOF' Follow-up from PR # — auto-proposed from the code review. **Finding:** @@ -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. - + 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 "" \ - --body-file - \ - [--label ""] <<'EOF' + [--label ""] \ + --body-file - <<'EOF' Follow-up from PR # — auto-proposed from the code review. **Finding:**