git-workflow

Enforce standardized Git branching, commit, and pull request workflows.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/az9713/my-agent-skills --skill git-workflow-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/az9713/my-agent-skills/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/az9713/my-agent-skills --skill git-workflow-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflows are often inconsistent, leading to merge conflicts and unclear review processes.

Core Features & Use Cases

  • Branching strategy guidance, naming conventions, and merge rules to maintain a clean history across repositories.
  • Commit conventions and PR guidelines that standardize reviews, reduce rework, and speed up releases.
  • Examples and safe-guarded workflows for feature branches, hotfixes, and release branches you can apply in multi-repo teams.

Quick Start

Switch to the develop branch, create a feature branch, commit changes with the specified format, and open a PR following the guidelines.

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 for branching and pull requests?▼

A standardized Git workflow defines branch naming conventions, commit message formats, and PR guidelines to maintain a clean history and reduce merge conflicts across repositories.

How do I set up commit conventions and branch naming rules for feature branches?▼

You can enforce commit conventions and branch naming rules by applying standardized workflow guidelines that specify formats for feature branches, hotfixes, and release branches.

Can I use this Git workflow for multi-repo teams with protected branches?▼

Yes, this workflow is designed for multi-repo teams and includes safety checks such as protected-branch rules and controlled release processes across multiple repositories.

What's the best way to manage merge strategies and code reviews in Git?▼

The best way to manage merge strategies and code reviews is to standardize PR descriptions and merge rules, which clarifies the review process and reduces rework before releases.

When do I need a specific branch for hotfixes versus feature development?▼

You need a dedicated hotfix branch for urgent production issues and a feature branch for standard development, following safe-guarded workflows to keep the repository history clean.

Why does inconsistent Git workflow cause merge conflicts and unclear reviews?▼

Inconsistent Git workflows cause merge conflicts and unclear reviews because they lack standardized branching strategies, commit conventions, and PR guidelines across team members.