chinese-git-workflow

Standardize Git workflows across Gitee, Coding.net, JiHu GitLab, and CNB.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/OnClickListener2048/confluence-mcp --skill chinese-git-workflow-onclicklistener2048
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chinese-git-workflow
Source: https://github.com/OnClickListener2048/confluence-mcp/tree/main/.claude/skills/chinese-git-workflow
Command: npx skills add https://github.com/OnClickListener2048/confluence-mcp --skill chinese-git-workflow-onclicklistener2048

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

国内团队在使用 Git 时经常遇到跨平台不稳定、国外工作流落地困难、commit message 缺乏规范等问题。本技能提供一套完整适配国内平台和团队习惯的 Git 工作流。

Core Features & Use Cases

  • 国内平台对接与兼容性
  • 多平台配置与分支策略示例
  • 工作流方案选型(主干开发、Git Flow、国内简化流程)
  • 提升协作效率与代码质量的实践案例

Quick Start

配置好本地 Git 用户信息并在仓库中应用选定的工作流方案。

Frequently Asked Questions about chinese-git-workflow

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

FAQPage Schema
How do I standardize Git workflow for Gitee and JiHu GitLab across multiple platforms?

To standardize Git workflow across Gitee and JiHu GitLab, apply platform-specific remotes, branch naming conventions, and MR/PR guidelines to reduce cross-platform friction and unify development processes.

What is the best Git branching strategy for small to mid-sized domestic teams?

For small to mid-sized domestic teams, a simplified domestic process or trunk-based development provides concrete branch naming and merging rules to improve collaboration efficiency over complex workflows.

How do I configure commit message guidelines and branch naming rules in local Git?

Configure commit message guidelines and branch naming rules by setting local Git user information and applying selected workflow schemes to the repository, enforcing consistent commit standards across the team.

Does this Git workflow support trunk-based development and Git Flow simultaneously?

Yes, the Git workflow supports both trunk-based development and Git Flow simultaneously, applying concrete branch naming and merging rules adaptable to various team scales and platform requirements.

Why does cross-platform Git collaboration cause friction on Coding.net and CNB?

Cross-platform Git collaboration causes friction on Coding.net and CNB due to inconsistent platform-specific remotes and varying MR/PR guidelines, requiring standardized workflow rules to unify the development process.