chinese-git-workflow

Standardizes Git workflows, commit messages, and CI/CD pipelines for Chinese hosting platforms.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill chinese-git-workflow-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chinese-git-workflow
Source: https://github.com/marcocpt/trae_skills/tree/main/chinese-git-workflow
Command: npx skills add https://github.com/marcocpt/trae_skills --skill chinese-git-workflow-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams in China often struggle with unstable GitHub access, CI/CD setups copied from foreign platforms that don't fit local tooling, and inconsistent mixed-language commit messages. This Skill provides a complete Git workflow adapted to domestic platforms like Gitee, Coding.net, JiHu GitLab, and CNB, along with team conventions for branching, commits, and code review. ## Core Features & Use Cases - Platform-Specific Configuration: Remote, SSH, and credential setup for Gitee, Coding.net, JiHu GitLab, and CNB, including dual-push mirroring to GitHub. - Branching Strategy Selection: Guidance for choosing between trunk-based development, Git Flow, and a simplified main/dev model based on team size and release cadence. - Chinese Conventional Commits: A localized commit message specification with type prefixes, scopes, and good/bad examples. - CI/CD Templates: Ready-to-adapt pipeline configurations for Gitee Go, Coding CI (Jenkinsfile), GitLab CI, and CNB's .cnb.yml, plus a mapping table from GitHub Actions concepts. - Use Case: A 10-person team migrating from GitHub to Gitee can use this Skill to configure remotes, adopt the simplified main/dev branching model, enforce Chinese conventional commits, and set up a Gitee Go pipeline with staging and production deployments. ## Quick Start Help me set up a Git workflow for my team on Gitee, including branch naming rules, Chinese commit message conventions, and a CI pipeline for the dev and main branches.

Frequently Asked Questions about chinese-git-workflow

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

FAQPage Schema
How do I choose a Git branching strategy for a small team?

For teams of 2-8 people with fast iteration and automated tests, trunk-based development works best: keep main always releasable and merge short-lived feature branches within 1-2 days. Larger teams with fixed release cycles should consider Git Flow or a simplified main/dev model.

How do I push to both Gitee and GitHub at the same time?

Add multiple push URLs to the same remote using git remote set-url --add --push origin for both the Gitee and GitHub repository URLs. Every git push then mirrors commits to both platforms automatically.

What is the Chinese conventional commits format?

It follows the pattern type(scope): description, using types like feat, fix, docs, refactor, perf, test, ci, and chore, with the description written in Chinese. The body can include context and links to task IDs such as TAPD-12345.

Does CNB support SSH for Git remotes?

No, CNB only supports HTTPS remote URLs in the form https://cnb.cool/<org>/<repo>.git. Authentication uses the fixed username cnb with a personal access token generated in the platform's settings as the password.

How do I migrate CI from GitHub Actions to Gitee Go or GitLab CI?

Map each GitHub Actions concept to its equivalent: triggers become Gitee Go triggers or GitLab only/rules, secrets become platform credential or CI/CD variable management, and manual runs map to when: manual in GitLab CI. The Skill provides a full comparison table and starter pipeline configs.

Why do Chinese filenames show as escaped characters in git status?

Git escapes non-ASCII filenames by default. Run git config --global core.quotepath false to display Chinese filenames correctly in status and diff output.