Release v0.3.10

.agents/skills/start/SKILL.md

@@ -40,12 +40,12 @@ After parsing flags, determine the active labels in this order:
 2. **Pool-based selection** — the allowed label pool is: `bug, documentation, enhancement, chore` (comma-separated). Select 1–3 labels from this pool that genuinely fit the task description and implementation approach. Do not apply labels mechanically — pick only what fits. If no pool label fits the task, fall through to step 3.
    - If any selected label name contains a space (e.g. `good first issue`), quote the entire `--label` value.
 3. **No label / creation** — if the pool is empty or no pool label fits:
-   - If `false` is `true` (case-insensitive string match): the agent **may** create a new label before applying it:
+   - If label creation is allowed (`false` = `true`, case-insensitive): the agent **may** create a new label before applying it:
      ```bash
      gh label create "<name>" --color "<hex>" --description "<short description>"
      ```
      Use judgment — only create a label with clear reuse value. Do not create near-duplicates of existing pool labels.
-   - If `false` is `false` or unset: omit `--label` entirely. Proceed silently; do not inform the user.
+   - Otherwise (`false` = `false` or unset): omit `--label` entirely. Proceed silently; do not inform the user.
 
 **Milestone resolution (three-tier, Case A only):**
 
@@ -228,6 +228,6 @@ When done, say: **"The code is ready for review. Please run `make dev` and test
 - If already on a feature branch when `/start` is invoked, warn the user before creating another branch.
 - `gh issue create` must use `--title` and `--body` flags. Never open an interactive editor.
 - 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 create if `false` is `true`). Never apply a label not in `bug, documentation, enhancement, chore` unless `false` is `true`.
+- 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: 97886867 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: start | adapter: codex | hash: f2589650 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->

.claude/commands/start.md

@@ -35,12 +35,12 @@ After parsing flags, determine the active labels in this order:
 2. **Pool-based selection** — the allowed label pool is: `bug, documentation, enhancement, chore` (comma-separated). Select 1–3 labels from this pool that genuinely fit the task description and implementation approach. Do not apply labels mechanically — pick only what fits. If no pool label fits the task, fall through to step 3.
    - If any selected label name contains a space (e.g. `good first issue`), quote the entire `--label` value.
 3. **No label / creation** — if the pool is empty or no pool label fits:
-   - If `false` is `true` (case-insensitive string match): the agent **may** create a new label before applying it:
+   - If label creation is allowed (`false` = `true`, case-insensitive): the agent **may** create a new label before applying it:
      ```bash
      gh label create "<name>" --color "<hex>" --description "<short description>"
      ```
      Use judgment — only create a label with clear reuse value. Do not create near-duplicates of existing pool labels.
-   - If `false` is `false` or unset: omit `--label` entirely. Proceed silently; do not inform the user.
+   - Otherwise (`false` = `false` or unset): omit `--label` entirely. Proceed silently; do not inform the user.
 
 **Milestone resolution (three-tier, Case A only):**
 
@@ -223,6 +223,6 @@ When done, say: **"The code is ready for review. Please run `make dev` and test
 - If already on a feature branch when `/start` is invoked, warn the user before creating another branch.
 - `gh issue create` must use `--title` and `--body` flags. Never open an interactive editor.
 - 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 create if `false` is `true`). Never apply a label not in `bug, documentation, enhancement, chore` unless `false` is `true`.
+- 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: 972bf405 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: start | adapter: claude | hash: 5be63054 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->

.cursor/rules/start.mdc

@@ -41,12 +41,12 @@ After parsing flags, determine the active labels in this order:
 2. **Pool-based selection** — the allowed label pool is: `bug, documentation, enhancement, chore` (comma-separated). Select 1–3 labels from this pool that genuinely fit the task description and implementation approach. Do not apply labels mechanically — pick only what fits. If no pool label fits the task, fall through to step 3.
    - If any selected label name contains a space (e.g. `good first issue`), quote the entire `--label` value.
 3. **No label / creation** — if the pool is empty or no pool label fits:
-   - If `false` is `true` (case-insensitive string match): the agent **may** create a new label before applying it:
+   - If label creation is allowed (`false` = `true`, case-insensitive): the agent **may** create a new label before applying it:
      ```bash
      gh label create "<name>" --color "<hex>" --description "<short description>"
      ```
      Use judgment — only create a label with clear reuse value. Do not create near-duplicates of existing pool labels.
-   - If `false` is `false` or unset: omit `--label` entirely. Proceed silently; do not inform the user.
+   - Otherwise (`false` = `false` or unset): omit `--label` entirely. Proceed silently; do not inform the user.
 
 **Milestone resolution (three-tier, Case A only):**
 
@@ -229,6 +229,6 @@ When done, say: **"The code is ready for review. Please run `make dev` and test
 - If already on a feature branch when `/start` is invoked, warn the user before creating another branch.
 - `gh issue create` must use `--title` and `--body` flags. Never open an interactive editor.
 - 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 create if `false` is `true`). Never apply a label not in `bug, documentation, enhancement, chore` unless `false` is `true`.
+- 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: ab5b210e | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: start | adapter: cursor | hash: 3b391b5c | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->

.gemini/skills/start/SKILL.md

@@ -40,12 +40,12 @@ After parsing flags, determine the active labels in this order:
 2. **Pool-based selection** — the allowed label pool is: `bug, documentation, enhancement, chore` (comma-separated). Select 1–3 labels from this pool that genuinely fit the task description and implementation approach. Do not apply labels mechanically — pick only what fits. If no pool label fits the task, fall through to step 3.
    - If any selected label name contains a space (e.g. `good first issue`), quote the entire `--label` value.
 3. **No label / creation** — if the pool is empty or no pool label fits:
-   - If `false` is `true` (case-insensitive string match): the agent **may** create a new label before applying it:
+   - If label creation is allowed (`false` = `true`, case-insensitive): the agent **may** create a new label before applying it:
      ```bash
      gh label create "<name>" --color "<hex>" --description "<short description>"
      ```
      Use judgment — only create a label with clear reuse value. Do not create near-duplicates of existing pool labels.
-   - If `false` is `false` or unset: omit `--label` entirely. Proceed silently; do not inform the user.
+   - Otherwise (`false` = `false` or unset): omit `--label` entirely. Proceed silently; do not inform the user.
 
 **Milestone resolution (three-tier, Case A only):**
 
@@ -228,6 +228,6 @@ When done, say: **"The code is ready for review. Please run `make dev` and test
 - If already on a feature branch when `/start` is invoked, warn the user before creating another branch.
 - `gh issue create` must use `--title` and `--body` flags. Never open an interactive editor.
 - 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 create if `false` is `true`). Never apply a label not in `bug, documentation, enhancement, chore` unless `false` is `true`.
+- 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: f1cddff1 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: start | adapter: gemini | hash: 25eab174 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->

VERSION

@@ -1 +1 @@
-0.3.9
+0.3.10

skills/start.md

@@ -48,12 +48,12 @@ After parsing flags, determine the active labels in this order:
 2. **Pool-based selection** — no label pool is configured. Fall through to step 3.
 {{/if}}
 3. **No label / creation** — if the pool is empty or no pool label fits:
-   - If `{{TICKET_LABEL_CREATION_ALLOWED}}` is `true` (case-insensitive string match): the agent **may** create a new label before applying it:
+   - If label creation is allowed (`{{TICKET_LABEL_CREATION_ALLOWED}}` = `true`, case-insensitive): the agent **may** create a new label before applying it:
      ```bash
      gh label create "<name>" --color "<hex>" --description "<short description>"
      ```
      Use judgment — only create a label with clear reuse value. Do not create near-duplicates of existing pool labels.
-   - If `{{TICKET_LABEL_CREATION_ALLOWED}}` is `false` or unset: omit `--label` entirely. Proceed silently; do not inform the user.
+   - Otherwise (`{{TICKET_LABEL_CREATION_ALLOWED}}` = `false` or unset): omit `--label` entirely. Proceed silently; do not inform the user.
 {{#if !TICKET_LABELS}}
 
 > **Tip:** Run `/setup` to populate TICKET_LABELS from your repo's existing GitHub labels.
@@ -291,7 +291,7 @@ When done, say: **"The code is ready for review. Please run `{{DEV_CMD}}` and te
 - `gh issue create` must use `--title` and `--body` flags. Never open an interactive editor.
 - 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`.
 {{#if TICKET_LABELS}}
-- Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `{{TICKET_LABELS}}` → omit (or create if `{{TICKET_LABEL_CREATION_ALLOWED}}` is `true`). Never apply a label not in `{{TICKET_LABELS}}` unless `{{TICKET_LABEL_CREATION_ALLOWED}}` is `true`.
+- Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `{{TICKET_LABELS}}` → omit (or, when `{{TICKET_LABEL_CREATION_ALLOWED}}` = `true`, create). Never apply a label outside `{{TICKET_LABELS}}` unless `{{TICKET_LABEL_CREATION_ALLOWED}}` = `true`.
 {{/if}}
 {{#if !TICKET_LABELS}}
 - Apply labels only when explicitly provided via `--label`. No label pool is configured.