What problem does it solve? Manually naming and basing git branches leads to inconsistent conventions and wrong base branches, especially in teams following Gitflow with stories, epics, hotfixes, and releases. This Skill automates branch creation with correct naming patterns and base-branch selection. ## Core Features & Use Cases - Automatic branch type detection: Accepts story files, epic files, task documents, raw descriptions, or explicit --hotfix/--release flags and derives the correct branch type and name. - Context-aware base branch selection: Detects sub-story relationships and epic integration branches, then prompts the user with recommended base options (develop, current feature branch, or epic integration branch). - Safety checks and worktree support: Halts on uncommitted changes, handles linked git worktrees, creates and pushes epic integration branches when needed, and cooperates with develop-pipeline locks. - Use Case: Run it with a story file like story.180.3.quick-re-search.md and get a properly named feature/story.180.3.quick-re-search branch cut from the right base, fetched and pushed to origin. ## Quick Start Ask the agent to create a branch from your story file, for example: create a branch for story.180.3.quick-re-search-functionality.md.