skills.rest
ChanningHe
ChanningHeCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Standardize commit messages, branch naming, and PR review processes.

Updated Jan 1, 2026
Search Tags:#git#workflow#branching#commits#best-practices#code-review#pull-requests
One-click install
npx skills add https://github.com/ChanningHe/dotfiles --skill git-workflow-channinghe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ChanningHe/dotfiles/tree/main/claude/skills/git-workflow
Command: npx skills add https://github.com/ChanningHe/dotfiles --skill git-workflow-channinghe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git workflow standards help teams maintain a clean, predictable history and reduce friction in collaboration by enforcing consistent commit messages, branch naming, and review practices.

Core Features & Use Cases

  • Commit Message Format: enforce type-prefix and subject length to improve traceability.
  • Branch Strategy: define naming conventions and lifecycle (feature, fix, hotfix, refactor) to minimize conflicts.
  • Pull Request Standards: require reviewers and templates to ensure code review quality.
  • Git Best Practices: guidelines for amend, rebase, and ignore rules to keep main clean.

Quick Start

Adopting these standards in your repository by aligning commits, branches, and PRs.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize Git commit messages and branch naming for my team?▼

Standardize Git workflows by enforcing commit type-prefixes and subject length rules, while defining branch naming conventions to improve traceability and minimize merge conflicts across teams.

What is the best way to reduce Git merge conflicts in collaborative projects?▼

Reduce Git merge conflicts by adopting a clear branch lifecycle strategy covering feature, fix, hotfix, and refactor branches to minimize friction and maintain a clean main branch.

How do I set up pull request standards and code review templates?▼

Set up pull request standards by requiring designated reviewers and applying PR templates to enforce consistent code review quality and ensure adherence to project best practices across teams.

When should I use Git amend and rebase to keep the main branch clean?▼

Use Git amend and rebase as part of Git best practices to keep main clean by modifying recent commits and applying branch changes onto the updated base for a predictable project history.

Does this Git workflow standardization work for teams of various sizes?▼

Yes, this Git workflow standardization applies to teams of various sizes by scaling commit message formats, branch strategies, and pull request review processes to maintain collaboration quality.

Related Skills

Explore More Software Engineering Skills→
chaimtchaimt

speckit-git-initialize

Initialize a Git repository with an initial commit in the current directory.

Community
Intermediate
vikas-gits-goodvikas-gits-good

safe-workflow

Enforce SAFe-compliant branch naming, commit formatting, and rebase-first git workflows.

Community
Intermediate
greyhaven-aigreyhaven-ai
29

grey-haven-linear-workflow

Automate Linear issue creation, branch naming, and PR integration with Git workflows.

Community
Basic
richardnpaulrichardnpaul

git-workflow

Standardize Git branching, commit, and pull request practices for team workflows.

Community
Advanced