domains / families / devops / git-workflow

git-workflow

combined

Implement Git branching strategies, PR workflows, and release management patterns. Configure GitFlow, trunk-based development, or GitHub Flow for team collaboration. Use when establishing version control workflows or improving development team collaboration. This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team collaboration.

When to use

• Establishing team Git workflows
• Implementing branching strategies
• Configuring pull request processes
• Setting up release management
• Improving code review practices

When not to use

• Guidance executes against real environments: confirm target, blast radius, and rollback plan before applying anything.
• Never deploy to production without explicit approval. Docs-only import: upstream scripts and templates not bundled.

Skill page

Conflict

The copies overlap on Conventional Commits and PR/branch basics, but each contains material steps the others lack. BagelHole and its mirror (sickn33) provide a full branching-strategy reference (Trunk, GitHub Flow, GitFlow), PR templates, branch protection, CODEOWNERS, and hooks. jezweb provides operational workflows for preparing PRs, cleaning merged branches, resolving conflicts, monorepo tags, .gitignore-first init, and private-repo license audit. brycewang provides a standards document with branch naming tables, daily/hotfix/release workflows, merge vs rebase policy, and conflict resolution steps. Crowning one would hide real alternatives, so the combined skill should include the reference material plus the operational workflows and standards.