From 5dbe29705278180e6abde8a7d48e6a7815b81d29 Mon Sep 17 00:00:00 2001 From: Sebastien Taggart Date: Sun, 7 Jun 2026 08:49:55 -0400 Subject: [PATCH] Auto-offer /submit-for-review at end of /start instead of requiring a separate command --- .agents/skills/start/SKILL.md | 14 ++++++++------ .claude/commands/start.md | 14 ++++++++------ .cursor/rules/start.mdc | 14 ++++++++------ .gemini/skills/start/SKILL.md | 14 ++++++++------ skills/github-agile/start.md | 12 +++++++----- 5 files changed, 39 insertions(+), 29 deletions(-) diff --git a/.agents/skills/start/SKILL.md b/.agents/skills/start/SKILL.md index 1da9cba..8a9a8e1 100644 --- a/.agents/skills/start/SKILL.md +++ b/.agents/skills/start/SKILL.md @@ -225,11 +225,10 @@ Show the user: `On branch feature/` 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 --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. - + diff --git a/.claude/commands/start.md b/.claude/commands/start.md index 7490823..abc45ad 100644 --- a/.claude/commands/start.md +++ b/.claude/commands/start.md @@ -220,11 +220,10 @@ Show the user: `On branch feature/` 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 --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. - + diff --git a/.cursor/rules/start.mdc b/.cursor/rules/start.mdc index 4620a9d..5375d49 100644 --- a/.cursor/rules/start.mdc +++ b/.cursor/rules/start.mdc @@ -226,11 +226,10 @@ Show the user: `On branch feature/` 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 --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. - + diff --git a/.gemini/skills/start/SKILL.md b/.gemini/skills/start/SKILL.md index 6108972..3b20315 100644 --- a/.gemini/skills/start/SKILL.md +++ b/.gemini/skills/start/SKILL.md @@ -225,11 +225,10 @@ Show the user: `On branch feature/` 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 --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. - + diff --git a/skills/github-agile/start.md b/skills/github-agile/start.md index aab4d77..758f9ae 100644 --- a/skills/github-agile/start.md +++ b/skills/github-agile/start.md @@ -284,11 +284,10 @@ Show the user: `On branch feature/` 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 ---