git-workflow

Standardize Git workflows across GitHub and Gitee with Conventional Commits.

6|1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/boshi-xixixi/agenticflow-skills --skill git-workflow-boshi-xixixi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/boshi-xixixi/agenticflow-skills/tree/main/skills/05_DevOps_GitWorkflow
Command: npx skills add https://github.com/boshi-xixixi/agenticflow-skills --skill git-workflow-boshi-xixixi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines Git version control and collaboration on platforms like GitHub and Gitee, ensuring code integrity and efficient teamwork.

Core Features & Use Cases

  • Standardized Commits: Enforces Conventional Commits for clear, machine-readable commit history.
  • Branching Strategies: Guides users on effective branching models like Trunk-Based Development.
  • Platform Integration: Provides best practices for GitHub and Gitee workflows, including PRs and CI/CD.
  • Use Case: A team can use this Skill to ensure all their commits follow a consistent format, making it easier to generate changelogs and understand the evolution of the codebase.

Quick Start

Use the git-workflow skill to help me create a feat commit for a new user authentication feature.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce Conventional Commits in my team's Git workflow?

To enforce Conventional Commits in your Git workflow, this Skill standardizes commit messages across GitHub and Gitee, ensuring a clear, machine-readable history. It guides users to structure commit messages consistently, making it easier to generate changelogs and understand codebase evolution.

What is the best way to manage GitHub pull requests and Gitee merge requests?

The best way to manage GitHub PRs and Gitee MRs is by using standardized platform collaboration workflows. This Skill facilitates efficient code reviews and PR/MR management by providing best practices and utilizing specialized agents for automated Git operations and platform interactions.

How do I implement a Trunk-Based Development branching strategy?

To implement Trunk-Based Development, this Skill guides users on effective branching models for version control. It helps standardize your branching strategies to streamline Git workflows and maintain code integrity across GitHub and Gitee platforms.

Does this Git workflow skill work with both GitHub and Gitee?

Yes, this Git workflow skill works with both GitHub and Gitee. It standardizes version control and platform collaboration across both platforms, enforcing Conventional Commits and providing best practices for code reviews, PR/MR management, and CI/CD integration.

Why should I use Conventional Commits for version control?

You should use Conventional Commits for version control because it enforces a clear, machine-readable commit history. This standardization makes it significantly easier to generate changelogs, understand the evolution of the codebase, and facilitate efficient teamwork on GitHub and Gitee.