GitHub Push Governance

Use this skill at the start or continuation of any coding, documentation, repository, project setup, feature, bug fix, refactor, skill creation, or file-generation task that may produce versioned work.

This is an iron rule: at key moments, ask about GitHub repository creation/use, keep README quality high, route work to the correct branch, and push code with a Simplified Chinese summary when appropriate.

Semantic Trigger Rule

Trigger by meaning, not exact keywords. Apply this skill when the user is starting a new project/session, creating or editing code/docs/skills/config/scripts/README files, asking to save work, mentioning GitHub/git/repo/push/commit, preparing delivery, packaging, deploying, releasing, or completing a meaningful milestone.

The following are examples, not a closed list. Any phrase with the same intent triggers this skill:

• 保存或留痕: 保存一下, 存一下, 留个版本, 备份一下, 保存进仓库, 同步一下, 同步代码, 同步到远端, 放到 GitHub, 传到 GitHub, 推上去, 提交一下, 提交记录.
• 建仓库或绑定远端: 新建项目, 开个仓库, 建个 repo, 建个 GitHub 仓库, 这个项目放哪, 帮我托管, 绑定远端, private 还是 public.
• 分支和合并: 这个功能要不要开分支, 直接在 test 改行不行, test 改完推哪, 合到线上, 合到主分支, 开 PR, 发 PR, merge, rebase.
• 发布和交付: 准备上线, 发版, 发包, 打包发布, 打 tag, 做 release, 交付一下, main 是不是用来发包, 线上分支.
• English equivalents: save progress, commit it, push it, sync changes, create repo, put it on GitHub, open a PR, tag it, release it, deploy it, which branch.

Do not run GitHub write operations for pure read-only analysis, pure Git/GitHub Q&A, or when the user explicitly says not to commit, push, create a repo, or publish. In those cases, answer or record the decision without repeatedly asking.