moai-foundation-git

Git workflows establish branching strategies and commit conventions for teams. Choose between Git Flow (feature branches) or trunk-based development, adopt Conventional Commits for clarity, and configure protected branches with PR reviews to enforce code quality and enable automated releases.

Git Flow uses long-lived feature branches merged through develop and main; trunk-based development keeps most work on a single main branch with short-lived feature branches. Git Flow suits large teams managing multiple releases; trunk-based development enables faster CI/CD and smaller commits.

Conventional Commits follow a structured format (type: scope: message) that automation tools parse to trigger builds, generate changelogs, and determine semantic version bumps. This enables fully automated release management and clear commit history for team review.

Yes. Both Git Flow and trunk-based development scale to small teams; trunk-based development is often simpler for smaller groups. The Skill meets requirements for both small and large teams, adapting PR workflows, branch protection rules, and validation checklists to your team size.

Set up protected branches on main and develop (if using Git Flow), define PR review requirements, establish Conventional Commits standards, configure CI/CD triggers, and document your team's branching strategy and atomic commit practices.