create-branch

Creates git branches from up-to-date origin/main with reviewer-friendly naming conventions.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/kbukum/gokit --skill create-branch-kbukum
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-branch
Source: https://github.com/kbukum/gokit/tree/main/.github/skills/create-branch
Command: npx skills add https://github.com/kbukum/gokit --skill create-branch-kbukum

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about create-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a git branch from the latest main?▼

Run git fetch origin first to refresh remote refs, then git switch -c <branch-name> origin/main. This guarantees the new branch starts from the newest main rather than a stale local checkout.

What is a good git branch naming convention?▼

Use a username prefix followed by a short kebab-case summary of the change, such as kbukum/storage-gcs-backend. Avoid batch numbers, plan numbers, task IDs, and session-specific detail that mean nothing to reviewers.

Can I base a new branch on another feature branch instead of main?▼

Yes, but only when the request explicitly says to stack on another branch. Fetch origin, then run git switch -c <branch-name> origin/<base-branch> and keep that base branch current.

What happens to uncommitted changes when switching branches?▼

Uncommitted changes follow you onto the new branch. Check git status before switching to confirm the carried-over edits are intentional and not unrelated work.

Does this skill commit or push the new branch?▼

No. It only creates the branch and leaves edits uncommitted. The maintainer commits, pushes, and opens a pull request only when explicitly asked.