git-workflow

A standardized Git workflow enforces consistent branching, commit messaging, and pull request processes across multiple contributors. You need it to prevent confusing project histories, minimize merge conflicts, and ensure efficient feature, fix, and release coordination.

Set up Git branching conventions by applying defined prefixes like feature/, bugfix/, and hotfix/ to organize work. This skill detects existing project conventions and provides concrete branching guidelines with ready-to-use command examples to keep your repository structured.

The best way to write conventional commit messages is to follow a standardized style that produces readable history and enables automated changelog generation. This skill provides concrete commit messaging guidelines to enforce consistency across your project contributors.

Yes, you can use this skill with existing project conventions. It actively detects project conventions such as CONTRIBUTING.md files, PR templates, and README sections, then applies the specified branch, commit, and PR workflows to your feature and release cycle.

Enforce pull request reviews and tests by applying standardized PR templates and checks. This skill provides templates to ensure reviews, tests, and documentation are included, coordinating feature development and bug fixes with minimal conflicts.