What problem does it solve? Starting new work often means manually inspecting uncommitted changes, picking a branch naming convention, and running several git commands. This Skill automates that flow by deriving a categorized branch name from a description, ticket/issue link, or your current uncommitted and ahead-of-base work, then creating and publishing the branch. ## Core Features & Use Cases - Argument-driven branching: Accepts a free-form description or a ticket/issue link (GitHub, Linear, Jira) and derives the branch category and slug from it. - Change-aware naming: With no argument, it analyzes uncommitted changes and ahead-of-base commits to infer a category (feature, fix, refactor, docs, test, chore, perf, build, ci) and a kebab-case slug. - Safety checks and publishing: Blocks when there is nothing to branch from or when already on a work branch, pulls the latest remote state, creates the branch, and pushes it with upstream tracking. - Use Case: You paste a Linear ticket link and say "start a branch for this" — the Skill reads the ticket, infers the category, and creates and pushes something like feature/add-oauth-login. ## Quick Start Ask the agent to create a new branch from your ticket link or current uncommitted changes, for example: "Start a new branch for this work."