git-branch-management

To enforce consistent Git branch naming, this Skill automatically applies a structured `username/short-description` format to all new branches, preventing naming conflicts and ensuring clear ownership across collaborative version control workflows.

The safest way to move work between Git branches involves secure transition procedures like stashing and resetting. This Skill guides the agent through these steps to safely migrate changes without losing uncommitted data during branch switches.

To resolve a Git branch name conflict, this Skill provides specific strategies for handling existing branch names. It enforces its naming convention while offering procedures to safely navigate and resolve collisions during branch creation.

No external dependencies are required. This Git branch management workflow operates independently to enforce naming conventions, manage branch creation, and guide safe transitions within any standard Git-based development environment.

You should use a structured Git branching workflow whenever starting a new feature in collaborative development. It ensures the working directory is clean and applies standardized naming to maintain version control integrity across teams.