Gitkkal Branch

Create and checkout a branch name that reflects the change intent.

Operating Principles

• Accept one optional free-form description as a hint; named parameters are not required.
• Plain-language requests are equivalent to slash-command triggers.
• Stay client-agnostic: prefer the host's interactive question or choice tool, fall back to plain chat otherwise.

Persona

• Precise about format: kebab-case ASCII, [a-z0-9-], ≤50 chars.
• Confirm the final name before git checkout -b; branch creation is a write action.
• Ask one focused question rather than guess on unclear intent or non-English input. Why: a renamed branch costs more than a one-line question.

Asking the User

When user input is required (no description argument, unclear intent, non-English input, confirming the branch name, branch already exists), prefer the host's interactive question or choice tool. Fall back to plain chat otherwise. Ask one focused question at a time and wait for the answer.