branch-create
Feature Branch Creation
Create a feature branch linked to an issue with a consistent naming convention. Works in any Git repository.
Workflow
Step 1: Collect Input
Gather the issue number for the branch name.
- Ask the user for the issue number. If provided as an argument, use it directly.
- If the issue number is provided, verify it exists with
gh issue view <number>. If the issue does not exist, inform the user and stop. - Derive a short description from the issue title automatically. Only ask the user for a description if the issue has no title.
Step 2: Generate Branch Name
Generate the branch name following the project's naming convention.
- Default convention:
feature/<issue-number>-<description> - Convert the description to lowercase kebab-case:
- Replace spaces and underscores with hyphens
- Remove special characters
- Collapse consecutive hyphens
If the project has a different convention documented (e.g., in CLAUDE.md or CONTRIBUTING.md), follow that convention instead.
Step 3: Create and Checkout
- If a branch with the same name already exists, inform the user and ask whether to:
- Checkout the existing branch, or
- Choose a different name
- Create the branch from the current HEAD:
git checkout -b <branch-name> - Display the branch name and associated issue number.
Constraints
- Do not push the branch to remote automatically. The user decides when to push.
- Do not modify the issue (no labels, no assignees) -- branch creation is the only action.
More from caldiaworks/caldiaworks-marketplace
ideation
Turn rough ideas into structured, validated idea documents through collaborative dialogue. Explores context, asks clarifying questions one at a time, proposes alternative approaches with feasibility evaluation, and produces documents ready for requirements definition. Use when: ideation, brainstorm, new idea, explore an idea, I want to build, what if we, let's think about, propose approaches, evaluate this idea, idea document, アイデア出し, 案出し, ブレスト, アイデアを整理, 検討したい.
36requirements-docx
Convert USDM/EARS requirements documents from Markdown to professionally formatted Word (.docx) files for client submission. Generates cover pages, table of contents, headers/footers, and styled requirement hierarchies. Leverages the docx skill for Word file generation. Use when: export requirements to Word, requirements to docx, USDM to Word, convert requirements document, 要件書をWord出力, 要件定義書のdocx変換, Word形式で要件書を作成, 要件定義書をWordに変換.
36usdm
Convert ambiguous user requests into structured USDM requirements documents. Decomposes requirements into Requirement -> Reason -> Description -> Specification hierarchy. Integrates with GitHub Issues, Asana, and Jira tickets as input sources. Use when: create requirements, write requirements document, USDM, decompose requirements, requirements definition, 要件定義, 要件を整理, 要件分解.
33issue-create
Create GitHub Issues from user input or USDM requirements documents. Standalone mode guides through title, body, and labels. USDM mode creates a hierarchy of issues from requirements with specifications in the issue body. Use when: create issue, new issue, GitHub issue, open issue, file issue, create issues from requirements, USDM to issues, issue-create, /issue-create.
20re-verify-logic
Verify logic diagrams against source code. Check line-number accuracy, Mermaid syntax, node completeness, and side effect documentation. Runs as independent Critic in fork context. Use when: verify logic, check logic diagram, validate phase 2, re-verify-logic.
19commit
Create focused git commits with change review, selective staging, and auto-drafted messages. Use when: commit, git commit, save changes, commit my work, make a commit, stage and commit, review changes before committing. Also use when the user says /commit or asks to commit specific files.
19