Auto-offer /submit-for-review at end of /start

.agents/skills/start/SKILL.md

@@ -225,11 +225,10 @@ Show the user: `On branch feature/<name>`
 
 Now write the code. Do NOT commit anything.
 
-When done, say: **"The code is ready for review. Please run `make dev` and test locally. Let me know if it looks good, needs changes, or should be scrapped. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
 
-- User says looks good → run `/submit-for-review`
-- User requests changes → iterate, repeat this message
-- User says scrap it → run `make abandon`
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -314,7 +313,10 @@ git branch --show-current
 
 Continue from where work left off. Do NOT commit.
 
-When done, say: **"The code is ready for review. Please run `make dev` and test locally. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
+
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -328,4 +330,4 @@ When done, say: **"The code is ready for review. Please run `make dev` and test
 - The issue is assigned to `@me` at creation. If you are creating a ticket on someone else's behalf, remove the assignee after creation with `gh issue edit <number> --remove-assignee @me`.
 - Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `bug, documentation, enhancement, chore` → omit `--label` entirely. Never apply a label outside `bug, documentation, enhancement, chore`.
 - Milestone resolution order: per-invocation flag → auto-detected from GitHub open milestones. Never prompt for a milestone more than once per invocation.
-<!-- generated by CodeCannon/sync.py | skill: start | adapter: codex | hash: 87978fe3 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: start | adapter: codex | hash: a708a5e4 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

.claude/commands/start.md

@@ -220,11 +220,10 @@ Show the user: `On branch feature/<name>`
 
 Now write the code. Do NOT commit anything.
 
-When done, say: **"The code is ready for review. Please run `make dev` and test locally. Let me know if it looks good, needs changes, or should be scrapped. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
 
-- User says looks good → run `/submit-for-review`
-- User requests changes → iterate, repeat this message
-- User says scrap it → run `make abandon`
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -309,7 +308,10 @@ git branch --show-current
 
 Continue from where work left off. Do NOT commit.
 
-When done, say: **"The code is ready for review. Please run `make dev` and test locally. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
+
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -323,4 +325,4 @@ When done, say: **"The code is ready for review. Please run `make dev` and test
 - The issue is assigned to `@me` at creation. If you are creating a ticket on someone else's behalf, remove the assignee after creation with `gh issue edit <number> --remove-assignee @me`.
 - Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `bug, documentation, enhancement, chore` → omit `--label` entirely. Never apply a label outside `bug, documentation, enhancement, chore`.
 - Milestone resolution order: per-invocation flag → auto-detected from GitHub open milestones. Never prompt for a milestone more than once per invocation.
-<!-- generated by CodeCannon/sync.py | skill: start | adapter: claude | hash: a5438057 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: start | adapter: claude | hash: 56496fd3 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

.cursor/rules/start.mdc

@@ -226,11 +226,10 @@ Show the user: `On branch feature/<name>`
 
 Now write the code. Do NOT commit anything.
 
-When done, say: **"The code is ready for review. Please run `make dev` and test locally. Let me know if it looks good, needs changes, or should be scrapped. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
 
-- User says looks good → run `/submit-for-review`
-- User requests changes → iterate, repeat this message
-- User says scrap it → run `make abandon`
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -315,7 +314,10 @@ git branch --show-current
 
 Continue from where work left off. Do NOT commit.
 
-When done, say: **"The code is ready for review. Please run `make dev` and test locally. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
+
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -329,4 +331,4 @@ When done, say: **"The code is ready for review. Please run `make dev` and test
 - The issue is assigned to `@me` at creation. If you are creating a ticket on someone else's behalf, remove the assignee after creation with `gh issue edit <number> --remove-assignee @me`.
 - Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `bug, documentation, enhancement, chore` → omit `--label` entirely. Never apply a label outside `bug, documentation, enhancement, chore`.
 - Milestone resolution order: per-invocation flag → auto-detected from GitHub open milestones. Never prompt for a milestone more than once per invocation.
-<!-- generated by CodeCannon/sync.py | skill: start | adapter: cursor | hash: a93864c9 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: start | adapter: cursor | hash: f4c0717b | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

.gemini/skills/start/SKILL.md

@@ -225,11 +225,10 @@ Show the user: `On branch feature/<name>`
 
 Now write the code. Do NOT commit anything.
 
-When done, say: **"The code is ready for review. Please run `make dev` and test locally. Let me know if it looks good, needs changes, or should be scrapped. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
 
-- User says looks good → run `/submit-for-review`
-- User requests changes → iterate, repeat this message
-- User says scrap it → run `make abandon`
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -314,7 +313,10 @@ git branch --show-current
 
 Continue from where work left off. Do NOT commit.
 
-When done, say: **"The code is ready for review. Please run `make dev` and test locally. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
+
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -328,4 +330,4 @@ When done, say: **"The code is ready for review. Please run `make dev` and test
 - The issue is assigned to `@me` at creation. If you are creating a ticket on someone else's behalf, remove the assignee after creation with `gh issue edit <number> --remove-assignee @me`.
 - Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `bug, documentation, enhancement, chore` → omit `--label` entirely. Never apply a label outside `bug, documentation, enhancement, chore`.
 - Milestone resolution order: per-invocation flag → auto-detected from GitHub open milestones. Never prompt for a milestone more than once per invocation.
-<!-- generated by CodeCannon/sync.py | skill: start | adapter: gemini | hash: d520b4ac | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->
+<!-- generated by CodeCannon/sync.py | skill: start | adapter: gemini | hash: 25457446 | DO NOT EDIT — run CodeCannon/sync.py to regenerate -->

skills/github-agile/start.md

@@ -284,11 +284,10 @@ Show the user: `On branch feature/<name>`
 
 Now write the code. Do NOT commit anything.
 
-When done, say: **"The code is ready for review. Please run `{{DEV_CMD}}` and test locally. Let me know if it looks good, needs changes, or should be scrapped. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
 
-- User says looks good → run `/submit-for-review`
-- User requests changes → iterate, repeat this message
-- User says scrap it → run `{{ABANDON_CMD}}`
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---
 
@@ -389,7 +388,10 @@ git branch --show-current
 
 Continue from where work left off. Do NOT commit.
 
-When done, say: **"The code is ready for review. Please run `{{DEV_CMD}}` and test locally. When you're happy, run `/submit-for-review` to commit, push, and open a PR."**
+When done, say: **"When you've verified locally, reply `yes` to submit, or say what to change."**
+
+- User replies `yes` → invoke `/submit-for-review` inline
+- User describes changes → iterate, repeat this message
 
 ---