Manage Git Flow

What problem does it solve?

Messy git histories due to inconsistent branching, vague commit messages, and ad-hoc merge practices slow teams down and hinder code reviews. This skill establishes a repeatable workflow that preserves a readable history and supports semantic versioning.

Core Features & Use Cases

• Starting a Task (Feature Branch): Create a clearly named feature or fix branch using the type/short-description convention, e.g., feat/add-login-ui or fix/auth-timeout.
• Work & Commit (Conventional Commits): Encourage small, atomic commits with semantic messages like feat(ui): add login panel or fix(auth): resolve token refresh timeout.
• Finishing a Task: Verify tests, run lint, and perform a merge strategy (squash/merge) back into main, followed by branch cleanup.
• Use Case: Maintain a clean, auditable project history in collaborative environments with frequent task handoffs and releases.

Quick Start

Create a feature branch named feat/add-login-ui, commit incremental changes with semantic messages, and complete the task by following the verify, lint, and merge steps.