What problem does it solve? Teams often create branches off stale local checkouts or name them with internal scaffolding like batch numbers and task IDs, producing confusing history and PRs that reviewers cannot understand as standalone changes. ## Core Features & Use Cases - Correct base selection: Always fetches origin and branches from the latest origin/main, or from an explicitly named base branch when stacking is requested. - Naming discipline: Enforces <username>/<short-change-summary> kebab-case names that describe the actual change, rejecting batch numbers, plan numbers, and session-local detail. - Clean handoff: Creates the branch and leaves edits uncommitted so the maintainer controls commits, pushes, and PR creation. - Use Case: You start work on a new storage backend feature. The skill fetches origin, creates kbukum/storage-gcs-backend from the latest main, and leaves your working tree ready for edits. ## Quick Start Ask the assistant to create a new branch for your change, for example by saying: create a branch for adding the GCS storage backend.