manage-branch

To enforce Git branch naming conventions, this Skill validates branch names against patterns like `mriley/<type>/<name>` during creation and switching. It automatically prefixes branches with the correct type, such as `feat/` or `fix/`, ensuring repository organization.

Switching Git branches with uncommitted changes requires safety checks to prevent data loss. This Skill checks for uncommitted modifications before switching and guides users through safe operations, offering options to handle or preserve changes.

Supported Git branch types for naming convention workflows include feature, fix, refactor, perf, chore, docs, and test. The Skill validates and formats branches using these specific types within the `mriley/<type>/<name>` pattern.

The best way to create a new feature branch with a strict naming format is to provide a descriptive name. The Skill automatically formats it as `mriley/feat/your-descriptive-name` and checks for uncommitted changes before proceeding.

Your Git workflow needs strict branch naming validation to prevent inconsistencies and improve repository organization. Enforcing conventions ensures all branches adhere to a predictable pattern, making it easier to track changes and manage collaboration.

This branch management approach works without external Git hooks by validating branch names directly during creation and switching. It enforces naming conventions and performs safety checks internally, independent of hook configurations.