Agent skill

Git Workflow for Chinese Platforms

by jnMetaCode in jnMetaCode/superpowers-zh

Reference for setting up Git on Gitee, Coding.net, JiHu GitLab and CNB, with branching models, branch naming and CI differences for teams in China.

MITAuto-check: warningsDevelopment

SKILL.md written in Chinese; this summary is our English description.

Install Git Workflow for Chinese Platforms

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add jnMetaCode/superpowers-zh --skill chinese-git-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jnMetaCode/superpowers-zh chinese-git-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/chinese-git-workflow .claude/skills/chinese-git-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
chinese-git-workflow
GitHub stars
8.3k
Token cost
~2.4k tokens
SKILL.md length
302 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Reference for setting up Git on Gitee, Coding.net, JiHu GitLab and CNB, with branching models, branch naming and CI differences for teams in China.

  • Works in 4 steps: 全部小写,用 - 连接单词(不用下划线或驼峰) → 前缀明确分支类型:feat/、fix/、hotfix/、release/ → 关联任务管理平台的编号(如有):feat/TAPD-12345-descripti… → …
  • Connecting a repository to Gitee, Coding.net, JiHu GitLab or CNB
  • SKILL.md covers 概述, 国内 Git 平台适配, 工作流选择 and 分支命名规范, plus 4 more sections
  • Calls git and npm; reaches gitee.com and registry.npmmirror.com

What it does

Written in Chinese, this reference is for teams that host code on domestic Git platforms. It compares Gitee, Coding.net, JiHu GitLab, CNB and GitHub on how reliably each can be reached from within China, free private repositories, CI/CD offering, review terminology and artifact registries, and it gives remote setup examples for each host. CNB is noted as HTTPS only, with no SSH.

It then lays out three branching approaches: trunk-based development for small teams, Git Flow for fixed release cadences, and a simplified main-plus-dev flow common among smaller Chinese teams, followed by branch naming rules such as lowercase words joined by hyphens. Per its description it also covers SSH and HTTPS credentials, CI setup and mirror sync, but the excerpt ends before those parts, and the skill is meant to run only when you invoke /chinese-git-workflow yourself.

When your agent uses it

  • Connecting a repository to Gitee, Coding.net, JiHu GitLab or CNB
  • Choosing between trunk-based development, Git Flow and a simplified dev and main flow
  • Setting branch naming rules for a team that works on a domestic Git host

Example prompts

  • “Add a Gitee remote for this project and explain how its CI differs from GitHub Actions.”
  • “Which branching model suits our team of five on JiHu GitLab?”
  • “Set up a mirror of our GitHub repo on CNB over HTTPS.”

Requirements

  • Git

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. 全部小写,用 - 连接单词(不用下划线或驼峰)
  2. 前缀明确分支类型:feat/、fix/、hotfix/、release/
  3. 关联任务管理平台的编号(如有):feat/TAPD-12345-description
  4. 长度适中,能看出分支目的即可

What it can do on your machine

Read from SKILL.md and the folder at commit fe34019. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • gitee.com
    • registry.npmmirror.com
    • github.com
    • e.coding.net
    • jihulab.com
    • cnb.cool
    • github.com.proxy

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git Workflow for Chinese Platforms loads about 2.4k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 302 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: warnings

The automated check found patterns that need a careful read before installing.

  • WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:39
    # ~/.ssh/config
  • WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:43
    IdentityFile ~/.ssh/gitee_rsa
  • NoteMentions a .env fileSKILL.md:530
    .env
  • NoteMentions a .env fileSKILL.md:531
    .env.local
  • NoteMentions a .env fileSKILL.md:532
    .env.*.local

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jnMetaCode/superpowers-zh at commit fe34019, republished under its MIT licence (© jnMetaCode). 302 words, ~2,383 tokens.

Download SKILL.mdSave it as .claude/skills/chinese-git-workflow/SKILL.md (or your agent's skills folder).
name
chinese-git-workflow
description
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用,不要根据上下文自动触发。
version
1.0.0
license
MIT

国内 Git 工作流规范

概述

国内团队用 Git 经常踩的坑:GitHub 访问不稳定、CI/CD 方案照搬国外水土不服、commit message 中英混杂没有规范。本技能提供一套完整适配国内平台和团队习惯的 Git 工作流。

核心原则: 工作流服务于团队效率,不是为了流程而流程。选适合团队规模的,别硬套大厂方案。

国内 Git 平台适配

平台对比
特性GiteeCoding.net极狐 GitLabCNBGitHub
国内访问快快快快不稳定
免费私有仓库有有有有有
CI/CDGitee GoCoding CI内置 GitLab CI内置(.cnb.yml)GitHub Actions
代码审查PRMRMRMRPR
制品库有限完整完整完整Packages
适合场景开源/小团队中大型团队企业私有化云原生 / Docker 流水线国际项目
Gitee 特有配置
bash
# 设置 Gitee 远程仓库
git remote add origin https://gitee.com/<org>/<repo>.git

# Gitee 的 SSH 配置
# ~/.ssh/config
Host gitee.com
    HostName gitee.com
    User git
    IdentityFile ~/.ssh/gitee_rsa
    PreferredAuthentications publickey

# 同时推送到 Gitee 和 GitHub(镜像同步)
git remote set-url --add --push origin https://gitee.com/<org>/<repo>.git
git remote set-url --add --push origin https://github.com/<org>/<repo>.git
Coding.net 特有配置
bash
# Coding 的仓库地址格式
git remote add origin https://e.coding.net/<team>/<project>/<repo>.git

# Coding 支持的 SSH 地址
git remote add origin git@e.coding.net:<team>/<project>/<repo>.git
极狐 GitLab 特有配置
bash
# 极狐 GitLab 私有化部署常见地址格式
git remote add origin https://jihulab.com/<group>/<repo>.git

# 或者企业内部部署
git remote add origin https://gitlab.yourcompany.com/<group>/<repo>.git
CNB(Cloud Native Build)特有配置
bash
# CNB 仓库地址(仅支持 HTTPS,不提供 SSH 协议)
git remote add origin https://cnb.cool/<org>/<repo>.git

# HTTPS 认证:用户名固定为 cnb,密码为个人访问令牌(Access Token)
# 在 CNB 平台 → 个人设置 → 访问令牌 中生成
git config credential.helper store

工作流选择

方案一:主干开发(Trunk-Based Development)

适合: 小团队(2-8 人)、迭代速度快、有完善的自动化测试。

main ──●──●──●──●──●──●──●──●──●──
        \   /  \   /       \   /
feat/x  ●─●   ●─●    fix/y ●─●
(短命分支,1-2 天内合回)

规则:

  • 主干(main)始终保持可发布状态
  • 功能分支生命周期不超过 2 天
  • 每天至少合并一次到主干
  • 用 Feature Flag 控制未完成功能的可见性
bash
# 从 main 拉分支
git checkout -b feat/user-login main

# 开发完成后,rebase 到最新 main
git fetch origin
git rebase origin/main

# 提交 PR/MR,合并后删除分支
方案二:Git Flow(经典分支模型)

适合: 中大团队、版本发布节奏固定(如双周迭代)、需要维护多个版本。

main     ──●────────────────●────────────── 生产环境
            \              / \
release     ●──●──●──●──●    ●──●──●──●── 发布分支
            \              /
develop  ──●──●──●──●──●──●──●──●──●──●── 开发主线
             \   /  \       /
feat/x       ●─●    ●─────●               功能分支
                      \   /
                  fix/y ●─●                修复分支

分支说明:

  • main — 生产环境代码,只接受 release 和 hotfix 的合并
  • develop — 开发主线,功能分支从这里拉出,合回这里
  • release/* — 发布分支,从 develop 拉出,只修 bug 不加功能
  • feat/* — 功能分支
  • hotfix/* — 紧急修复,从 main 拉出,同时合回 main 和 develop
方案三:国内团队常用简化流程

适合: 大多数国内中小团队的实际情况。

main     ──●──────●──────●──── 生产环境(受保护)
            \    / \    /
dev      ──●──●─●──●──●─●──── 开发/测试环境
             \  /    \  /
feat/x       ●●      ●●       功能分支

规则:

  • main 分支受保护,只能通过 PR/MR 合并
  • dev 分支对应测试环境,自动部署
  • 功能分支从 dev 拉出,合回 dev
  • dev 测试通过后,合并到 main 进行发布

分支命名规范

国内团队常用命名
bash
# 功能分支
feat/user-login              # 新功能
feat/JIRA-1234-order-refund  # 关联任务编号

# 修复分支
fix/payment-callback         # Bug 修复
fix/JIRA-5678-null-pointer   # 关联 Bug 编号

# 发布分支
release/v2.1.0               # 版本发布
release/2024-03-sprint       # 按迭代命名

# 紧急修复
hotfix/v2.0.1                # 线上紧急修复
hotfix/fix-login-crash       # 描述性命名

# 个人分支(部分团队使用)
dev/zhangsan/feat-login      # 个人开发分支
命名规则
  1. 全部小写,用 - 连接单词(不用下划线或驼峰)
  2. 前缀明确分支类型:feat/、fix/、hotfix/、release/
  3. 关联任务管理平台的编号(如有):feat/TAPD-12345-description
  4. 长度适中,能看出分支目的即可

中文 Commit Message 规范

约定式提交(Conventional Commits)中文版
<类型>(<范围>): <简要描述>
                                    ← 空行
<正文(可选)>
                                    ← 空行
<脚注(可选)>
类型清单
类型说明emoji(可选)
feat新增功能✨
fix修复 Bug🐛
docs文档更新📝
style代码格式(不影响逻辑)💄
refactor重构(不是新功能也不是修 Bug)♻️
perf性能优化⚡
test测试相关✅
build构建系统或外部依赖📦
ciCI/CD 配置👷
chore其他杂项🔧
revert回滚⏪
好的 commit message
feat(购物车): 支持批量删除商品

- 新增全选/反选功能
- 删除操作增加二次确认弹窗
- 批量删除接口使用 POST /cart/batch-delete

关联需求:TAPD-12345
fix(支付): 修复微信支付在 iOS 16 上无法唤起的问题

原因:微信 SDK 8.0.33 版本在 iOS 16 上 Universal Links 校验逻辑变更,
导致 openURL 回调失败。

方案:升级 SDK 至 8.0.38,并更新 Associated Domains 配置。

Closes #567
不好的 commit message
# 太笼统
update code
fix bug
修改了一些东西

# 没有上下文
fix: 修复问题
feat: 新增功能

# 中英混杂无规范
fix:修复了一个bug,因为user login的时候会crash

CI/CD 平台适配

Gitee Go
yaml
# .gitee/pipelines/pipeline.yml
name: 构建与测试
displayName: '构建与测试流水线'

triggers:
  push:
    branches:
      include:
        - main
        - dev

stages:
  - name: 测试
    jobs:
      - name: 单元测试
        steps:
          - step: npmbuild@1
            name: install_and_test
            displayName: '安装依赖并执行测试'
            inputs:
              nodeVersion: 20
              commands:
                - npm ci
                - npm test
Coding CI
groovy
// Jenkinsfile(Coding CI 支持 Jenkinsfile 语法)
pipeline {
    agent any

    stages {
        stage('安装依赖') {
            steps {
                sh 'npm ci'
            }
        }

        stage('单元测试') {
            steps {
                sh 'npm test'
            }
        }

        stage('构建') {
            steps {
                sh 'npm run build'
            }
        }

        stage('部署到测试环境') {
            when {
                branch 'dev'
            }
            steps {
                sh './scripts/deploy-staging.sh'
            }
        }

        stage('部署到生产环境') {
            when {
                branch 'main'
            }
            steps {
                sh './scripts/deploy-production.sh'
            }
        }
    }

    post {
        failure {
            // 企业微信/钉钉通知
            sh './scripts/notify-failure.sh'
        }
    }
}
极狐 GitLab CI
yaml
# .gitlab-ci.yml
stages:
  - test
  - build
  - deploy

variables:
  NODE_IMAGE: node:20-alpine
  # 使用国内镜像加速
  NPM_REGISTRY: https://registry.npmmirror.com

单元测试:
  stage: test
  image: $NODE_IMAGE
  script:
    - npm config set registry $NPM_REGISTRY
    - npm ci
    - npm test
  coverage: '/Lines\s*:\s*(\d+\.?\d*)%/'

构建:
  stage: build
  image: $NODE_IMAGE
  script:
    - npm config set registry $NPM_REGISTRY
    - npm ci
    - npm run build
  artifacts:
    paths:
      - dist/

部署测试环境:
  stage: deploy
  script:
    - ./scripts/deploy-staging.sh
  only:
    - dev
  environment:
    name: staging

部署生产环境:
  stage: deploy
  script:
    - ./scripts/deploy-production.sh
  only:
    - main
  environment:
    name: production
  when: manual  # 生产环境手动触发
CNB(Cloud Native Build)
yaml
# .cnb.yml — branch-first 结构,直接指定 Docker 镜像跑流水线
main:
  push:
    - docker:
        image: node:20
      stages:
        - npm ci
        - npm test
        - npm run build
  pull_request:
    - docker:
        image: node:20
      stages:
        - npm run lint
        - npm test

特点:

  • 每个流水线独立指定 Docker 镜像,天然云原生
  • 支持 push / pull_request 触发
  • 同一事件可并行多条流水线
  • stages 也支持 - name: xxx + script: 的展开形式,复杂场景见官方文档
GitHub Actions 国内替代方案对照
GitHub Actions 功能Gitee GoCoding CI极狐 GitLab CICNB
触发条件triggersJenkinsfile triggersonly/rulespush / pull_request
缓存依赖cache stepstash/unstashcache见官方文档
制品存储artifacts制品库artifacts见官方文档
环境变量envenvironmentvariablesenv
密钥管理环境变量配置凭据管理CI/CD VariablesAccess Token
手动触发手动运行手动触发when: manual页面手动运行

PR/MR 描述模板

中文模板

在仓库中创建 PR/MR 模板文件:

Gitee: .gitee/PULL_REQUEST_TEMPLATE.md

Coding / GitLab: .gitlab/merge_request_templates/default.md

markdown
## 变更说明

<!-- 简要描述这次改动做了什么,解决了什么问题 -->

## 变更类型

- [ ] 新功能(feat)
- [ ] Bug 修复(fix)
- [ ] 重构(refactor)
- [ ] 性能优化(perf)
- [ ] 文档更新(docs)
- [ ] 其他:

## 关联信息

- 需求/Bug 链接:
- 设计文档:

## 改动范围

<!-- 列出主要改动的模块和文件 -->

## 测试情况

- [ ] 单元测试通过
- [ ] 手动测试通过
- [ ] 相关模块回归测试通过

## 测试方法

<!-- 描述如何验证这次改动 -->

## 影响范围

<!-- 这次改动可能影响哪些功能?是否需要通知其他团队? -->

## 部署注意事项

- [ ] 需要执行数据库迁移
- [ ] 需要更新配置文件
- [ ] 需要更新环境变量
- [ ] 无特殊注意事项

## 截图/录屏

<!-- 如果涉及 UI 变更,贴截图或录屏 -->

常用 Git 配置

国内环境优化
bash
# 设置用户信息
git config --global user.name "张三"
git config --global user.email "zhangsan@company.com"

# commit message 编辑器设置为 VS Code
git config --global core.editor "code --wait"

# 解决中文文件名显示为转义字符的问题
git config --global core.quotepath false

# 设置默认分支名
git config --global init.defaultBranch main

# 代理设置(如果需要同时使用 GitHub)
git config --global http.https://github.com.proxy socks5://127.0.0.1:7890

# NPM 使用国内镜像
npm config set registry https://registry.npmmirror.com
.gitignore 国内项目常见配置
gitignore
# IDE
.idea/
.vscode/
*.swp

# 依赖
node_modules/
vendor/

# 构建产物
dist/
build/
*.exe

# 环境配置
.env
.env.local
.env.*.local

# 系统文件
.DS_Store
Thumbs.db
desktop.ini

# 国内平台特有
.coding/

检查清单

在推送代码前,确认:

  • 分支命名符合团队规范
  • commit message 格式正确,类型和范围准确
  • 关联了对应的需求/Bug 编号
  • PR/MR 描述填写完整
  • CI 流水线通过
  • 已请求相关同事 Review

© jnMetaCode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/chinese-git-workflow of jnMetaCode/superpowers-zh.

Open the folder on GitHubat commit fe34019

Compare with similar skills

Git Workflow for Chinese Platforms next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git Workflow for Chinese Platforms compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Workflow for Chinese Platforms this skilljnMetaCode/superpowers-zh8.3k—~2.4kAutomated safety check: WarnMIT
Pypi ReleasealchemiststudiosDOTai/tunacode125—~2.2kAutomated safety check: PassMIT
npm Package Publisherklaudworks/universal-skills181—~923Automated safety check: PassMIT
Push and PyPI Releaseliaohch3/claude-tap3.3k—~509Automated safety check: PassMIT
PR Createposit-dev/skills529—~4.3kAutomated safety check: WarnMIT
Git WorkflowsTencentCloudBase/CloudBase-AI-Toolkit1.1k—~3kAutomated safety check: PassMIT

Similar skills

  • Pypi Release

    alchemiststudiosDOTai/tunacode

    This skill should be used when releasing tunacode-cli to PyPI.

    125 GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • npm Package Publisher

    klaudworks/universal-skills

    Releases an npm package by committing changes, bumping the version with npm version, pushing the tag and checking the GitHub Actions publish.

    181 GitHub stars~923 tokensUpdated 8 mo ago
    DevelopmentAuto-check passed
  • Push and PyPI Release

    liaohch3/claude-tap

    Pushes the current work to GitHub and, when pending commits change code, bumps the version in pyproject.toml so CI publishes a new PyPI release.

    3.3k GitHub stars~509 tokensUpdated 15 days ago
    DevelopmentAuto-check passed
  • PR Create

    posit-dev/skills

    Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes.

    529 GitHub stars~4.3k tokensUpdated today
    DevelopmentAuto-check: warnings
  • Git Workflows

    TencentCloudBase/CloudBase-AI-Toolkit

    Reusable git delivery workflows derived from local slash commands (commit, push, PR, release notes, GitHub Actions failure triage with worktree-based fixes, and isolating your own changes from a…

    1.1k GitHub stars~3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Git Workflow

    EliasOulkadi/shokunin

    Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body…

    114 GitHub stars~2.4k tokensUpdated 2 days ago
    DevelopmentAuto-check: notes

More from jnMetaCode/superpowers-zh

All 21 skills in this repo
  • Brainstorming Before Building

    jnMetaCode/superpowers-zh

    Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.

    8.3k GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed
  • Git Worktree Isolation

    jnMetaCode/superpowers-zh

    Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.

    8.3k GitHub starsUsed in 1 repo~982 tokens
    Auto-check passed
  • Inline Plan Execution

    jnMetaCode/superpowers-zh

    Executes a written implementation plan task by task in the current session, with a progress ledger, test-first gates and one fresh-context review at the end.

    8.3k GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed
  • Agency Orchestrator Workflow Runner

    jnMetaCode/superpowers-zh

    Runs agency-orchestrator YAML workflows inside the current agent session, with the session's own model playing each role in turn and no API key needed.

    8.3k GitHub starsUsed in 1 repo~885 tokens
    Auto-check passed
  • Chinese Code Review Etiquette

    jnMetaCode/superpowers-zh

    Gives Chinese-language templates and priority labels for code review feedback, plus guidance on bilingual comments, commit messages and common team anti-patterns.

    8.3k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed
  • Chinese Commit Conventions

    jnMetaCode/superpowers-zh

    Reference for Chinese-language git commits and changelogs: Conventional Commits adapted for Chinese teams, with templates, breaking-change notes and issue links for several platforms.

    8.3k GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Git Workflow for Chinese Platforms

What does Git Workflow for Chinese Platforms do?

Reference for setting up Git on Gitee, Coding.net, JiHu GitLab and CNB, with branching models, branch naming and CI differences for teams in China. Written in Chinese, this reference is for teams that host code on domestic Git platforms.net, JiHu GitLab, CNB and GitHub on how reliably each can be reached from within China, free private repositories, CI/CD offering, review terminology and artifact registries, and it gives remote setup examples for each host.

When should I use Git Workflow for Chinese Platforms?

Git Workflow for Chinese Platforms fits situations like: connecting a repository to Gitee, Coding.net, JiHu GitLab or CNB; choosing between trunk-based development, Git Flow and a simplified dev and main flow; setting branch naming rules for a team that works on a domestic Git host.

How do I install Git Workflow for Chinese Platforms in Claude Code?

Run `npx skills add jnMetaCode/superpowers-zh --skill chinese-git-workflow -a claude-code`. Or copy the skill folder (skills/chinese-git-workflow in jnMetaCode/superpowers-zh) into .claude/skills/chinese-git-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Git Workflow for Chinese Platforms in Codex?

Run `npx skills add jnMetaCode/superpowers-zh --skill chinese-git-workflow -a codex`. Or copy the skill folder (skills/chinese-git-workflow in jnMetaCode/superpowers-zh) into .agents/skills/chinese-git-workflow in your project. Codex loads it when a task matches its description.

Can I use Git Workflow for Chinese Platforms in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jnMetaCode/superpowers-zh --skill chinese-git-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chinese-git-workflow, .gemini/skills/chinese-git-workflow, .github/skills/chinese-git-workflow and .opencode/skills/chinese-git-workflow in your project.

What does Git Workflow for Chinese Platforms need to run?

Going by SKILL.md and its folder, Git Workflow for Chinese Platforms needs the command-line tools its instructions call (git and npm). Our summary lists: Git.

Does Git Workflow for Chinese Platforms access the network?

SKILL.md names 7 domains. In commands or code: gitee.com, registry.npmmirror.com, github.com, e.coding.net, jihulab.com, cnb.cool and github.com.proxy; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Git Workflow for Chinese Platforms safe to install?

Our automated static check of SKILL.md flagged 2 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.

What licence does Git Workflow for Chinese Platforms use?

Git Workflow for Chinese Platforms is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Workflow for Chinese Platforms use?

About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git Workflow for Chinese Platforms?

Skills that share tags, products or a category with Git Workflow for Chinese Platforms: Pypi Release (alchemiststudiosDOTai/tunacode, 125 stars), npm Package Publisher (klaudworks/universal-skills, 181 stars), Push and PyPI Release (liaohch3/claude-tap, 3.3k stars) and PR Create (posit-dev/skills, 529 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Workflow for Chinese Platforms?

jnMetaCode (a GitHub user) maintains it in jnMetaCode/superpowers-zh, which has 8,265 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 4, 2026.

Source: jnMetaCode/superpowers-zh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.