git-workflow

Standardize Git branching, commit messages, and pull request workflows.

100|8|Updated Apr 28, 2025

Search Tags:#git #workflow #branching #best-practices #code-review #pull-request

One-click install

npx skills add https://github.com/mcpc-tech/mcpc --skill git-workflow-mcpc-tech

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/mcpc-tech/mcpc/tree/main/.agent/skills/git-workflow
Command: npx skills add https://github.com/mcpc-tech/mcpc --skill git-workflow-mcpc-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git workflow inconsistencies lead to merge conflicts, stalled reviews, and unpredictable releases. This skill provides a standardized set of branching strategies, commit message conventions, and pull request processes to streamline collaboration and deliverables.

Core Features & Use Cases

Branching Strategy: Clear guidelines for main/master, develop, feature/, release/, and hotfix/* branches to manage work and releases.
Commit Message Hygiene: Enforces conventional commit style to improve changelogs and traceability.
Review & Merge Process: Defines PR requirements, code reviews, approvals, and merge strategies to ensure quality.
Use Case: A multi-developer project uses feature branches and code reviews to safely integrate changes into develop and prepare for release.

Quick Start

Describe your desired Git workflow to adopt. For example:

Create a feature branch from develop: git checkout develop && git pull --rebase && git checkout -b feature/my-feature
Commit messages follow the format feat(scope): subject or fix(scope): subject
Open a pull request against develop and require at least one review
Merge to develop after approval and run tests

Frequently Asked Questions about git-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a standardized Git workflow and when do I need branching strategies?▼

Standardize Git commit messages using conventional commit formats like feat(scope): subject or fix(scope): subject. This practice improves traceability and automates changelog generation for your repository.

How do I create a feature branch and open a pull request safely?▼

Define pull request procedures by requiring at least one code review approval before merging. This ensures code quality and safe integration of changes into develop or release branches.

Can I use this Git workflow for multi-repo integration?▼

Yes, this Git workflow applies to multi-repo integration in modern development environments. It standardizes merge strategies and branch naming across repositories to streamline collaboration and deliverables.

What's the best way to manage release and hotfix branches?▼

Manage release and hotfix branches by creating distinct release/* and hotfix/* branches from your main codebase. This isolates release stabilization and urgent fixes from active feature development.