branch

Installation
SKILL.md

Branch

  1. Check the current branch, git status, and task details.
  2. Name it. A name from the user wins as given. Otherwise <ticket-id>-<short-kebab-summary>, or just the summary if there's no ticket. Follow the repo's existing naming style.
  3. Fetch, then branch from the latest default branch unless the user says otherwise.
  4. If the branch already exists, switch to it and note any commits it has beyond the base.
  5. Report the branch name, its base, and any uncommitted work that was present.

Rules

  • Never stash, discard, or force through uncommitted work. If switching is blocked, stop and ask.
  • Never invent ticket IDs. If a ticket exists but its ID isn't visible, ask; if no human is available, proceed without it and say so in the report.
Installs
195
GitHub Stars
212
First Seen
May 9, 2026
branch — owainlewis/blueprint