Auto-post follow-up cross-link comment on originating issue

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

@@ -348,6 +348,27 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - If one or more issues were created: `"Created N follow-up issue(s): #X, #Y, #Z"`.
 - If the user chose `none` or all creations were skipped: say nothing further, proceed to end.
 
+**Post a cross-link comment on the originating issue.** If one or more follow-ups were created **and** a linked originating issue number was identified in Step 3, post a single comment on that issue listing the new follow-ups so a reader of the thread can see the trailing work without digging into the PR. Skip silently if no follow-ups were created or no originating issue is linked.
+
+Use your file-writing tool (not Bash) to create `<tmpdir>/followup_link_comment.md` (same temp directory from Step 6):
+
+```markdown
+## Follow-up tickets from PR #<merged-pr-number>
+
+The code review on the PR for this issue surfaced non-blocking items tracked separately:
+
+- #<f1> — <title1>
+- #<f2> — <title2>
+```
+
+Then post via the comment-posting script (do NOT use `gh issue comment` with `--body` or heredocs):
+
+```
+python3 CodeCannon/skills/github-agile/scripts/post-issue-comment.py <originating-issue-number> <tmpdir>/followup_link_comment.md
+```
+
+Use the unqualified `#N` form for all issue and PR references in the body. If `/submit-for-review` is later run again against the same originating issue and produces more follow-ups, a separate comment is posted then — comments accumulate naturally on the thread, each referencing its own PR.
+
 ---
 
 ## Important constraints
@@ -359,4 +380,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 actionable findings (WARNINGs in `ai` mode, plus CRITICALs in `advisory` mode). Never prompt the user for follow-ups when the review blocked the merge — those findings should be fixed, not ticketed. NOTEs never become follow-up tickets.
-<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: codex | hash: 35d89f6d | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: codex | hash: 818aec3b | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

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

@@ -343,6 +343,27 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - If one or more issues were created: `"Created N follow-up issue(s): #X, #Y, #Z"`.
 - If the user chose `none` or all creations were skipped: say nothing further, proceed to end.
 
+**Post a cross-link comment on the originating issue.** If one or more follow-ups were created **and** a linked originating issue number was identified in Step 3, post a single comment on that issue listing the new follow-ups so a reader of the thread can see the trailing work without digging into the PR. Skip silently if no follow-ups were created or no originating issue is linked.
+
+Use your file-writing tool (not Bash) to create `<tmpdir>/followup_link_comment.md` (same temp directory from Step 6):
+
+```markdown
+## Follow-up tickets from PR #<merged-pr-number>
+
+The code review on the PR for this issue surfaced non-blocking items tracked separately:
+
+- #<f1> — <title1>
+- #<f2> — <title2>
+```
+
+Then post via the comment-posting script (do NOT use `gh issue comment` with `--body` or heredocs):
+
+```
+python3 CodeCannon/skills/github-agile/scripts/post-issue-comment.py <originating-issue-number> <tmpdir>/followup_link_comment.md
+```
+
+Use the unqualified `#N` form for all issue and PR references in the body. If `/submit-for-review` is later run again against the same originating issue and produces more follow-ups, a separate comment is posted then — comments accumulate naturally on the thread, each referencing its own PR.
+
 ---
 
 ## Important constraints
@@ -354,4 +375,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 actionable findings (WARNINGs in `ai` mode, plus CRITICALs in `advisory` mode). Never prompt the user for follow-ups when the review blocked the merge — those findings should be fixed, not ticketed. NOTEs never become follow-up tickets.
-<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: claude | hash: 7245af88 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: claude | hash: 4e6d71d5 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

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

@@ -349,6 +349,27 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - If one or more issues were created: `"Created N follow-up issue(s): #X, #Y, #Z"`.
 - If the user chose `none` or all creations were skipped: say nothing further, proceed to end.
 
+**Post a cross-link comment on the originating issue.** If one or more follow-ups were created **and** a linked originating issue number was identified in Step 3, post a single comment on that issue listing the new follow-ups so a reader of the thread can see the trailing work without digging into the PR. Skip silently if no follow-ups were created or no originating issue is linked.
+
+Use your file-writing tool (not Bash) to create `<tmpdir>/followup_link_comment.md` (same temp directory from Step 6):
+
+```markdown
+## Follow-up tickets from PR #<merged-pr-number>
+
+The code review on the PR for this issue surfaced non-blocking items tracked separately:
+
+- #<f1> — <title1>
+- #<f2> — <title2>
+```
+
+Then post via the comment-posting script (do NOT use `gh issue comment` with `--body` or heredocs):
+
+```
+python3 CodeCannon/skills/github-agile/scripts/post-issue-comment.py <originating-issue-number> <tmpdir>/followup_link_comment.md
+```
+
+Use the unqualified `#N` form for all issue and PR references in the body. If `/submit-for-review` is later run again against the same originating issue and produces more follow-ups, a separate comment is posted then — comments accumulate naturally on the thread, each referencing its own PR.
+
 ---
 
 ## Important constraints
@@ -360,4 +381,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 actionable findings (WARNINGs in `ai` mode, plus CRITICALs in `advisory` mode). Never prompt the user for follow-ups when the review blocked the merge — those findings should be fixed, not ticketed. NOTEs never become follow-up tickets.
-<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: cursor | hash: a8d30b62 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: cursor | hash: e0c2aa23 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

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

@@ -348,6 +348,27 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - If one or more issues were created: `"Created N follow-up issue(s): #X, #Y, #Z"`.
 - If the user chose `none` or all creations were skipped: say nothing further, proceed to end.
 
+**Post a cross-link comment on the originating issue.** If one or more follow-ups were created **and** a linked originating issue number was identified in Step 3, post a single comment on that issue listing the new follow-ups so a reader of the thread can see the trailing work without digging into the PR. Skip silently if no follow-ups were created or no originating issue is linked.
+
+Use your file-writing tool (not Bash) to create `<tmpdir>/followup_link_comment.md` (same temp directory from Step 6):
+
+```markdown
+## Follow-up tickets from PR #<merged-pr-number>
+
+The code review on the PR for this issue surfaced non-blocking items tracked separately:
+
+- #<f1> — <title1>
+- #<f2> — <title2>
+```
+
+Then post via the comment-posting script (do NOT use `gh issue comment` with `--body` or heredocs):
+
+```
+python3 CodeCannon/skills/github-agile/scripts/post-issue-comment.py <originating-issue-number> <tmpdir>/followup_link_comment.md
+```
+
+Use the unqualified `#N` form for all issue and PR references in the body. If `/submit-for-review` is later run again against the same originating issue and produces more follow-ups, a separate comment is posted then — comments accumulate naturally on the thread, each referencing its own PR.
+
 ---
 
 ## Important constraints
@@ -359,4 +380,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 actionable findings (WARNINGs in `ai` mode, plus CRITICALs in `advisory` mode). Never prompt the user for follow-ups when the review blocked the merge — those findings should be fixed, not ticketed. NOTEs never become follow-up tickets.
-<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: gemini | hash: f2f2bd8f | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: submit-for-review | adapter: gemini | hash: d4292428 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

skills/github-agile/submit-for-review.md

@@ -388,6 +388,27 @@ If a single `gh issue create` call fails, report the failure for that finding an
 - If one or more issues were created: `"Created N follow-up issue(s): #X, #Y, #Z"`.
 - If the user chose `none` or all creations were skipped: say nothing further, proceed to end.
 
+**Post a cross-link comment on the originating issue.** If one or more follow-ups were created **and** a linked originating issue number was identified in Step 3, post a single comment on that issue listing the new follow-ups so a reader of the thread can see the trailing work without digging into the PR. Skip silently if no follow-ups were created or no originating issue is linked.
+
+Use your file-writing tool (not Bash) to create `<tmpdir>/followup_link_comment.md` (same temp directory from Step 6):
+
+```markdown
+## Follow-up tickets from PR #<merged-pr-number>
+
+The code review on the PR for this issue surfaced non-blocking items tracked separately:
+
+- #<f1> — <title1>
+- #<f2> — <title2>
+```
+
+Then post via the comment-posting script (do NOT use `gh issue comment` with `--body` or heredocs):
+
+```
+python3 CodeCannon/skills/github-agile/scripts/post-issue-comment.py <originating-issue-number> <tmpdir>/followup_link_comment.md
+```
+
+Use the unqualified `#N` form for all issue and PR references in the body. If `/submit-for-review` is later run again against the same originating issue and produces more follow-ups, a separate comment is posted then — comments accumulate naturally on the thread, each referencing its own PR.
+
 ---
 
 ## Important constraints