diff --git a/.agents/skills/start/SKILL.md b/.agents/skills/start/SKILL.md index 98f039c..a84d3e8 100644 --- a/.agents/skills/start/SKILL.md +++ b/.agents/skills/start/SKILL.md @@ -138,7 +138,7 @@ Now create the feature branch: gh issue develop --base dev --name feature/ --checkout ``` -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout dev` on its own does not influence which branch the new feature branch is cut from. +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout dev` on its own does not influence which branch the new feature branch is cut from. Verify the branch was created: @@ -198,7 +198,7 @@ Find and check out the existing branch, or create a new one linked to the issue: gh issue develop --base dev --name feature/ --checkout ``` -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state. +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state. Verify: @@ -230,4 +230,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 (or, when `false` = `true`, create). Never apply a label outside `bug, documentation, enhancement, chore` unless `false` = `true`. - 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 5112d1d..ccd7f07 100644 --- a/.claude/commands/start.md +++ b/.claude/commands/start.md @@ -133,7 +133,7 @@ Now create the feature branch: gh issue develop --base dev --name feature/ --checkout ``` -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout dev` on its own does not influence which branch the new feature branch is cut from. +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout dev` on its own does not influence which branch the new feature branch is cut from. Verify the branch was created: @@ -193,7 +193,7 @@ Find and check out the existing branch, or create a new one linked to the issue: gh issue develop --base dev --name feature/ --checkout ``` -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state. +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state. Verify: @@ -225,4 +225,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 (or, when `false` = `true`, create). Never apply a label outside `bug, documentation, enhancement, chore` unless `false` = `true`. - 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 c7b2b8f..7e2f615 100644 --- a/.cursor/rules/start.mdc +++ b/.cursor/rules/start.mdc @@ -139,7 +139,7 @@ Now create the feature branch: gh issue develop --base dev --name feature/ --checkout ``` -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout dev` on its own does not influence which branch the new feature branch is cut from. +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout dev` on its own does not influence which branch the new feature branch is cut from. Verify the branch was created: @@ -199,7 +199,7 @@ Find and check out the existing branch, or create a new one linked to the issue: gh issue develop --base dev --name feature/ --checkout ``` -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state. +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state. Verify: @@ -231,4 +231,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 (or, when `false` = `true`, create). Never apply a label outside `bug, documentation, enhancement, chore` unless `false` = `true`. - 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 3a0c733..74c21a3 100644 --- a/.gemini/skills/start/SKILL.md +++ b/.gemini/skills/start/SKILL.md @@ -138,7 +138,7 @@ Now create the feature branch: gh issue develop --base dev --name feature/ --checkout ``` -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout dev` on its own does not influence which branch the new feature branch is cut from. +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout dev` on its own does not influence which branch the new feature branch is cut from. Verify the branch was created: @@ -198,7 +198,7 @@ Find and check out the existing branch, or create a new one linked to the issue: gh issue develop --base dev --name feature/ --checkout ``` -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state. +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state. Verify: @@ -230,4 +230,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 (or, when `false` = `true`, create). Never apply a label outside `bug, documentation, enhancement, chore` unless `false` = `true`. - 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/start.md b/skills/start.md index abc5847..3003ca3 100644 --- a/skills/start.md +++ b/skills/start.md @@ -186,7 +186,9 @@ gh issue develop --name feature/ --checkout ``` {{/if}} -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout {{BRANCH_DEV}}` on its own does not influence which branch the new feature branch is cut from. +{{#if BRANCH_DEV}} +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state, so `git checkout {{BRANCH_DEV}}` on its own does not influence which branch the new feature branch is cut from. +{{/if}} Verify the branch was created: @@ -260,7 +262,9 @@ gh issue develop --name feature/ --checkout ``` {{/if}} -> `--base` is required when `BRANCH_DEV` is set: `gh issue develop` reads the default base from the GitHub API, not from local working state. +{{#if BRANCH_DEV}} +> `--base` is required: `gh issue develop` reads the default base from the GitHub API, not from local working state. +{{/if}} Verify: