git-workflow

Standardize Git branching, commits, and pull request practices for teams.

1|Updated Feb 11, 2026

Search Tags:#git #workflow #commit #branching #code-review #pull-request #rebasing

Ready to run

npx skills add https://github.com/xiaoshuangLi/aibo --skill git-workflow-xiaoshuangli

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git teams often struggle with inconsistent branching, vague commit messages, and tangled history. This skill provides standardized patterns to improve collaboration and code quality.

Core Features & Use Cases

Branch naming conventions
Conventional commit messages
Rebase and merge best practices
Pull request workflows and code review

Quick Start

Provide a feature branch name, write a conventional commit message, and open a pull request to start using this skill in your workflow.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I standardize commit message formats for my Git workflow?▼

To standardize commit messages in your Git workflow, enforce conventional commit formats through codified guidelines. This ensures clear, structured commit history by specifying message formats and naming conventions for all team members.

What are the best practices for Git branching and pull requests in team collaboration?▼

Best practices for Git branching and pull requests involve codifying feature branch naming conventions, enforcing code review protocols, and standardizing merge strategies. This maintains a clean history and improves collaborative code quality.

How do I write a conventional commit message for a feature branch?▼

Writing a conventional commit message for a feature branch requires following specified scope and format guidelines. You provide a feature branch name, write the formatted commit message, and open a pull request to complete the cycle.

Does this Git workflow skill support rebasing and merge strategies?▼

Yes, this Git workflow skill supports rebasing and merge strategies. It explicitly specifies scope across feature development, rebases, pull requests, and merge strategies to standardize release management and collaboration protocols.

How to manage tangled Git history and inconsistent branching?▼

To manage tangled Git history and inconsistent branching, apply standardized Git workflow patterns that codify branching, commits, and pull request practices. This resolves collaboration struggles by enforcing strict constraints and guidelines.