branchlisted

# Branch Start work on a new git branch, optionally in a new worktree. ## Arguments Accepts one of the following as arguments: - **Issue number**: e.g., `/branch 123` — fetches the issue title and derives the branch name - **Description**: e.g., `/branch add shellcheck support` — derives the branch name from the text - **Worktree flag**: append `--worktree` or `-w` to create a git worktree instead of a regular branch Examples: - `/branch 123` — branch from issue #123 - `/branch add dark mode toggle` — branch from description - `/branch 123 --worktree` — worktree from issue #123 - `/branch fix login redirect -w` — worktree from description ## Branch Naming Derive the branch name using this format: ```text <type>/<issue-number?>-<slug> ``` - **type**: Infer from context — `feat/`, `fix/`, `chore/`, `docs/`, `refactor/`, `perf/`, `test/`, `ci/` - If an issue has labels like `bug` → `fix/`, `enhancement` → `feat/`, `documentation` → `docs/` - If a description starts with a semantic prefix, use it - Default to `feat/` if unclear - **issue-number**: Include only if an issue number was provided - **slug**: Lowercase, hyphenated, max ~50 chars, derived from the issue title or description - Strip filler words when too long - e.g., "Add shellcheck support for shell scripts" → `add-shellcheck-support` Examples: - Issue #123 titled "feat(cli): add watch mode" → `feat/123-add-watch-mode` - Issue #45 labeled `bug`, titled "Parser crashes on empty input"