Git Workflow

Coordinate Git workflow tasks by recovering repository context, classifying user intent, routing to git-workflow skills, and enforcing safety gates for commit, push, PR/MR, tag, release, and branch protection operations.

Use when the user asks to choose, define, review, or document a Git branching model for a software project, including main/dev/feature/release/hotfix rules, single-developer vs team workflows, trunk-based development, protected branches, or branch naming policies. Do not use for committing code, opening PRs, tagging releases, or hotfix execution.

Use when the user asks for commit message help, commit scope conventions, atomic commit splitting, staged/unstaged diff review for commit boundaries, Conventional Commits validation, or installing/checking commit hooks. Do not use for creating PRs, pushing branches, release tagging, or branch strategy selection unless explicitly combined with a commit task.

Use when the user wants to start, continue, submit, push, or create a PR/MR for normal development work such as features, bug fixes, docs, tests, refactors, or build/CI changes. Handles feature/fix/docs/refactor branches and PRs into the configured integration branch, usually dev. Do not use for releases, tags, hotfixes from production, or detailed commit splitting.

Use when the user wants to publish a software release, promote changes from an integration branch to a stable branch, choose or validate a version number, create a release branch, generate release notes, create or validate tags, create GitHub/GitLab releases, or run release checklists. Do not use for normal feature PRs, daily commits, or emergency production hotfixes unless the hotfix is being released after repair.