Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .agents/skills/start/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ Now create the feature branch:
gh issue develop <number> --base dev --name feature/<short-descriptive-name> --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:

Expand Down Expand Up @@ -198,7 +198,7 @@ Find and check out the existing branch, or create a new one linked to the issue:
gh issue develop <number> --base dev --name feature/<short-name> --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:

Expand Down Expand Up @@ -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 <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 (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.
<!-- generated by CodeCannon/sync.sh | skill: start | adapter: codex | hash: f2589650 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
<!-- generated by CodeCannon/sync.sh | skill: start | adapter: codex | hash: 86f8546a | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
6 changes: 3 additions & 3 deletions .claude/commands/start.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ Now create the feature branch:
gh issue develop <number> --base dev --name feature/<short-descriptive-name> --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:

Expand Down Expand Up @@ -193,7 +193,7 @@ Find and check out the existing branch, or create a new one linked to the issue:
gh issue develop <number> --base dev --name feature/<short-name> --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:

Expand Down Expand Up @@ -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 <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 (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.
<!-- generated by CodeCannon/sync.sh | skill: start | adapter: claude | hash: 5be63054 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
<!-- generated by CodeCannon/sync.sh | skill: start | adapter: claude | hash: be9337a6 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
6 changes: 3 additions & 3 deletions .cursor/rules/start.mdc
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ Now create the feature branch:
gh issue develop <number> --base dev --name feature/<short-descriptive-name> --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:

Expand Down Expand Up @@ -199,7 +199,7 @@ Find and check out the existing branch, or create a new one linked to the issue:
gh issue develop <number> --base dev --name feature/<short-name> --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:

Expand Down Expand Up @@ -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 <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 (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.
<!-- generated by CodeCannon/sync.sh | skill: start | adapter: cursor | hash: 3b391b5c | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
<!-- generated by CodeCannon/sync.sh | skill: start | adapter: cursor | hash: 6fab1f6f | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
6 changes: 3 additions & 3 deletions .gemini/skills/start/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ Now create the feature branch:
gh issue develop <number> --base dev --name feature/<short-descriptive-name> --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:

Expand Down Expand Up @@ -198,7 +198,7 @@ Find and check out the existing branch, or create a new one linked to the issue:
gh issue develop <number> --base dev --name feature/<short-name> --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:

Expand Down Expand Up @@ -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 <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 (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.
<!-- generated by CodeCannon/sync.sh | skill: start | adapter: gemini | hash: 25eab174 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
<!-- generated by CodeCannon/sync.sh | skill: start | adapter: gemini | hash: d535ea99 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.3.10
0.3.11
8 changes: 6 additions & 2 deletions skills/start.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,9 @@ gh issue develop <number> --name feature/<short-descriptive-name> --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:

Expand Down Expand Up @@ -260,7 +262,9 @@ gh issue develop <number> --name feature/<short-name> --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:

Expand Down