Agent skill

Git Push

by yunshu0909 in yunshu0909/yunshu_skillshub

把项目推送到 GitHub，三种模式自动判断：首次推送（大文件扫描 → 生成 .gitignore → git init → gh 建仓 → 推送）、日常更新（commit + push）、版本发布（打 tag + 建 Release，可附下载文件）。核心原则是安全第一：推之前必扫大文件和敏感文件，宁可多问一句也不把不该推的东西推上去。当用户说"推到GitHub""推送到GitHub""git…

MITAuto-check: notesDevelopment

Install Git Push

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill git-push -a claude-code

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

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub git-push --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/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coding/git-push .claude/skills/git-push && 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/

Paste into Claude Code

Install the "git-push" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/git-push into .claude/skills/git-push/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-push", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/git-push

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill git-push -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub git-push --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/coding/git-push .agents/skills/git-push && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "git-push" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/git-push into .agents/skills/git-push/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-push", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill git-push -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub git-push --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/coding/git-push .cursor/skills/git-push && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "git-push" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/git-push into .cursor/skills/git-push/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-push", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/yunshu0909/yunshu_skillshub.git --path coding/git-push

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill git-push -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub git-push --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/coding/git-push .gemini/skills/git-push && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "git-push" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/git-push into .gemini/skills/git-push/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-push", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub git-push

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill git-push -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .github/skills && cp -r skills-src/coding/git-push .github/skills/git-push && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "git-push" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/git-push into .github/skills/git-push/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-push", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add yunshu0909/yunshu_skillshub --skill git-push -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install yunshu0909/yunshu_skillshub git-push --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/coding/git-push .opencode/skills/git-push && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "git-push" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/coding/git-push into .opencode/skills/git-push/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-push", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: git-push
GitHub stars: 767
Used in: 1 other repo
Token cost: ~1.7k tokens
SKILL.md length: 304 words
Files: 1
Skills in repo: 25
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 6 steps: 扫描先于一切 → 大文件主动拦截 → 公开仓库双重检查 → …
Tasks that involve Git workflow
SKILL.md covers 功能说明, 工作流程, 核心原则 and 使用示例
Calls git, gh and brew

What it does

Git Push is an agent skill from yunshu0909/yunshu_skillshub. 把项目推送到 GitHub，三种模式自动判断：首次推送（大文件扫描 → 生成 .gitignore → git init → gh 建仓 → 推送）、日常更新（commit + push）、版本发布（打 tag + 建 Release，可附下载文件）。核心原则是安全第一：推之前必扫大文件和敏感文件，宁可多问一句也不把不该推的东西推上去。当用户说"推到GitHub""推送到GitHub""git push""上传到GitHub""提交并推送""发版本""打release""打tag""/git-push"时触发。不适用于：规划哪些功能进哪个版本号（用 issue-pool——本 skill 只负责把已经定好的版本号打成 tag）、复杂 git 操作如 rebase/cherry-pick/解冲突/改历史/回滚（直接用 git 命令，本 skill 不覆盖）、代码写完前的自测和验收。

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow. It works with Git and GitHub. The repository describes itself as: 云舒精选的 Claude Code Skills 集合，提升开发和产品管理效率. The licence is MIT.

When your agent uses it

Tasks that involve Git workflow

Example prompts

“推到GitHub”
“推送到GitHub”
“git push”
“/git-push”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

扫描先于一切
大文件主动拦截
公开仓库双重检查
不破坏已有内容
每一步可中断
日常更新要轻

What it can do on your machine

Read from SKILL.md and the folder at commit da0d31f. 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
- gh
- brew
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
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 Push loads about 1.7k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 304 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:105

- `.env` / `.env.*` — 环境变量/密钥

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 yunshu0909/yunshu_skillshub at commit da0d31f, republished under its MIT licence (© yunshu0909). 304 words, ~1,705 tokens.

Download SKILL.mdSave it as .claude/skills/git-push/SKILL.md (or your agent's skills folder).

name: git-push
description: 把项目推送到 GitHub，三种模式自动判断：**首次推送**（大文件扫描 → 生成 .gitignore → git init → gh 建仓 → 推送）、**日常更新**（commit + push）、**版本发布**（打 tag + 建 Release，可附下载文件）。核心原则是安全第一：推之前必扫大文件和敏感文件，宁可多问一句也不把不该推的东西推上去。当用户说"推到GitHub""推送到GitHub""git push""上传到GitHub""提交并推送""发版本""打release""打tag""/git-push"时触发。不适用于：规划哪些功能进哪个版本号（用 issue-pool——本 skill 只负责把已经定好的版本号打成 tag）、复杂 git 操作如 rebase/cherry-pick/解冲突/改历史/回滚（直接用 git 命令，本 skill 不覆盖）、代码写完前的自测和验收。
metadata.status: active
metadata.status_updated_at: 2026-10-06

一键推送 GitHub

功能说明

把当前项目一键推送到 GitHub，覆盖完整生命周期：

首次推送 — 新项目从零到 GitHub
日常更新 — 改了文件，推一下（commit + push）
版本发布 — 打 tag + 创建 Release，可附带下载文件

核心原则：安全第一。宁可多问一句，不能把不该推的东西推上去。

工作流程

第0步：环境检查 + 模式判断

依次检查前置条件，任一不满足就终止并给出指引：

1. git 是否安装

❌ → 提示：brew install git，终止
✅ → 继续

2. gh CLI 是否安装

❌ → 提示：brew install gh，终止
✅ → 继续

3. gh 是否已登录 GitHub

执行 gh auth status 检查
❌ 未登录 → 提示：gh auth login，终止
✅ 已登录 → 记录账号名，告诉用户"当前登录账号：[xxx]"，继续

4. git 用户信息是否配置

执行 git config user.name 和 git config user.email 检查

❌ 未配置 → 提示用户设置：

git config --global user.name "你的名字"
git config --global user.email "你的邮箱"

终止

✅ 已配置 → 继续

5. 当前目录是否已是 git 仓库 → 决定走哪条路

不是 git 仓库 → 【首次推送】从第1步开始
是 git 仓库，无 remote → "本地有 git 但没关联远程"
    → 先执行第1步的大文件扫描（确保安全）
    → 再跳到第2步关联远程
是 git 仓库，有 remote → 【已有仓库】进入模式选择：
    ├── "推日常更新" → 跳到第3B步（日常更新）
    ├── "发新版本"   → 检查是否有未提交的变更
    │   ├── 有变更 → 先走第3B步，再走第4步
    │   └── 无变更 → 直接跳到第4步（只打 tag + Release）
    └── "重新来"
        → ⚠️ 警告："这将删除所有 Git 历史记录（包括所有提交、分支、tag），不可恢复。"
        → 用户二次确认后删除 .git，从第1步开始

第1步：项目扫描 + .gitignore 生成

⚠️ 铁律：.gitignore 必须在第一次 git add 之前就位。绝不能先提交再排除——Git 历史里的大文件删不干净，会导致仓库臃肿、推送失败。

1.1 扫描目录大小

用 du -sh 扫描所有顶级目录和文件，按大小排序。

大文件分级处理：

大小	处理方式
>10MB	列出，逐个问用户"要推吗？"
>50MB	额外警告"较大，推送会比较慢"
单文件 >100MB	必须排除，GitHub 硬限制，推不上去

展示格式（示例）：

扫描发现以下内容超过 10MB：

  1. 109MB  slides/   （PPT + 大图片）
  2.  12MB  assets/   （视频文件）

⚠️ 其中 slides/ 超过 50MB，推送会很慢。
❌ 其中 recording.mp4 (150MB) 超过 GitHub 100MB 单文件限制，必须排除。

要排除哪些？（输入序号，或 "全部排除" / "全部保留"）

1.2 敏感内容扫描（仅公开仓库）

如果用户选了公开仓库，额外扫描：

.env / .env.* — 环境变量/密钥
*secret* / *credential* / *token* — 密钥文件
*.pem / *.key — 证书文件
memory/ / MEMORY.md — AI 工具记忆文件
任何看起来像私人内容的文件

列出建议排除项，让用户逐项确认。

1.3 生成或更新 .gitignore

如果不存在 .gitignore：基于扫描结果生成新文件。

如果已存在 .gitignore：读取现有内容，将新增排除项合并进去，展示差异让用户确认。不覆盖用户已有的规则。

基础模板：

gitignore

# macOS
.DS_Store
.AppleDouble
.LSOverride
._*

# Editor
*.swp
*.swo
*~
.vscode/
.idea/

# [以下根据扫描结果动态生成]
# 大文件（用户确认排除）
[路径1]
[路径2]

# 敏感内容（仅公开仓库时）
[路径3]

展示给用户确认后写入文件。

第2步：用户决策

1. 仓库名（默认：当前目录名）

2. 描述（一句话，可留空）

3. 公开 / 私有

公开 → 二次确认："公开仓库所有人可见，确认 .gitignore 已排除敏感内容？"
- 不确认 → 回到第1.2步（敏感内容扫描）重新审查，完成后回到本步骤继续

4. 检查同名仓库

执行 gh repo view [账号]/[仓库名] 检查
❌ 不存在 → 继续
✅ 已存在 → 告诉用户，问：
- "换个名字" → 重新输入
- "用这个已有仓库" → 跳过创建，直接关联 remote（记录仓库 URL 供第3步使用）
- "删掉重建" → 需用户二次确认

第3步：推送

3A. 首次推送（新项目）

按以下顺序严格执行：

1. git init + git branch -m main
2. git add -A
3. git commit -m "init: 初始化 [仓库名]"
4. 创建远程仓库（如果第2步中仓库不存在）：
   gh repo create [仓库名] --private/--public --description "[描述]" --source=. --remote=origin
   （如果第2步中用户选了"用已有仓库"，跳过创建，直接：git remote add origin [已有仓库URL]）
5. git push -u origin main

3B. 日常更新（已有仓库）

1. 扫描变更：git status 查看改了什么
2. 检查新增大文件：
   - 新增文件中有 >10MB 的 → 问用户确认
   - 新增文件中有单文件 >100MB → 必须排除，加入 .gitignore
   - 如果修改了 .gitignore，确保 .gitignore 本身也在后续的 git add 范围内
3. git add -A
4. git commit -m "[根据变更内容自动生成提交信息]"
   - 提交信息规则：简洁明了，一句话概括主要变更
   - 示例："update: 新增用户模块 + 修复登录 bug"
5. git push

推送失败处理

错误	原因	处理
`rejected (fetch first)` 或 `non-fast-forward`	远程有本地没有的提交	默认执行 `git pull --rebase` 后重试
仍然失败 / 远程有冲突	历史不兼容	问用户"是否强制覆盖远程？" ⚠️ 告知："这将覆盖远程所有内容，仅在确认远程内容可以丢弃时使用"→ `git push --force`
超时/卡住	网络或仓库太大	检查仓库大小，建议排除大文件后重试
认证失败	token 过期	提示 `gh auth login`
`file exceeds 100MB`	单文件超限	提示具体文件名，加入 .gitignore，重新提交推送
`git add` 或 `git commit` 失败	文件异常/配置缺失	显示错误信息，引导用户排查

第4步：可选 — 版本发布（Release）

触发时机

首次推送后，主动问一次"需要打版本吗？"
日常更新后，不主动问（避免打扰）
用户主动说"发版本"、"打 release"、"打 tag"

流程

1. 确定版本号

读取当前已有的 tag（git tag --sort=-v:refname | head -5）

├── 没有任何 tag → 建议 v0.1.0
└── 已有 tag → 显示最近的版本，建议下一个（默认 minor +1）
    - v0.1.0 → 建议 v0.2.0
    - v1.2.3 → 建议 v1.3.0
    - 用户可自定义输入任意版本号

版本号说明（供用户参考）：
- v0.1.0 → v0.2.0  小更新（加了功能、改了内容）
- v0.2.0 → v1.0.0  大里程碑（首次正式发布、重大重构）
- v1.0.0 → v1.0.1  修修补补（修了个 bug）

2. Release 说明

自动读取自上个 tag 以来的 commit 记录（git log [上个tag]..HEAD --oneline）
生成变更摘要，让用户确认或修改
如果是第一个版本（无历史 tag），用所有 commit 生成摘要

3. 是否附带下载文件

需要附带可下载文件吗？（如 App 安装包、工具压缩包等）

├── 不需要 → 只打 tag + 创建 Release 页面
└── 需要 → 用户提供文件路径
    └── 检查文件是否存在 → 不存在则提示重新输入

4. 执行

git tag [version]
git push origin [version]
gh release create [version] --title "[仓库名] [version]" --notes "[Release 说明]"
# 如果有附件：
gh release upload [version] [文件路径]

Release 失败处理：

tag 已存在 → 提示用户"这个版本号已被使用"，让用户换一个
附件文件不存在 → 提示重新输入路径
其他错误 → 显示错误信息

完成输出

✅ 推送完成！

- 仓库：[URL]
- 可见性：私有 / 公开
- 文件数：[N] 个
- 仓库大小：[X]
- 排除项：[列出被 .gitignore 排除的内容]
- Release：[版本号 + URL] / 未创建

核心原则

1. 扫描先于一切

.gitignore 在第一次 git add 之前就位。大文件一旦进入 Git 历史，即使后来删除，仓库体积也不会缩小，会导致推送失败或极慢。已有 git 但未关联远程的项目，也要先扫描再推送。

2. 大文件主动拦截

10MB 以上主动问用户。50MB 以上警告慢，100MB 单文件是 GitHub 硬限制必须排除。日常更新时也要检查新增文件大小。

3. 公开仓库双重检查

公开仓库额外扫描敏感内容（密钥、AI 记忆文件、私人文档），并在推送前二次确认。

4. 不破坏已有内容

如果项目已有 .git 或 .gitignore，默认不覆盖，先问用户。删除 .git 等破坏性操作必须明确警告后果并二次确认。

5. 每一步可中断

用户随时可以说"停"或"回到上一步"。不要一口气跑完不给用户反应的机会。

6. 日常更新要轻

日常更新不问 Release、不问仓库名、不重新扫描全项目。只检查新增大文件，commit + push，快进快出。

使用示例

场景1：新项目首次推送

用户：帮我推到 GitHub

Skill：
→ 检查环境：git ✅ gh ✅ 已登录 ✅ git 用户已配置 ✅ 不是 git 仓库
→ 扫描项目...发现超过 10MB 的内容：
  - 85MB slides/ → 用户确认排除
  - 15MB images/ → 用户确认保留
→ 生成 .gitignore，用户确认
→ 仓库名：my-project，私有
→ 初始化 + 推送成功
→ "需要打 Release 吗？" → 跳过
→ ✅ 完成

场景2：日常更新

用户：推一下

Skill：
→ 检测到已关联远程仓库
→ 扫描变更：修改 3 个文件，新增 2 个文件（均 <10MB）
→ 提交信息："update: 新增用户模块 + 更新配置文件"
→ 推送成功
→ ✅ 完成

场景3：发版本

用户：打个 release

Skill：
→ 当前最新 tag：v0.1.0
→ "建议下一个版本号 v0.2.0，可以吗？"
→ 自动生成变更摘要（基于 commit 记录）
→ "需要附带下载文件吗？" → 不需要
→ 创建 tag + Release
→ ✅ Release v0.2.0 发布成功！

场景4：推送时发现大文件

→ git push 失败：file recording.mp4 exceeds 100MB
→ "recording.mp4 (150MB) 超过 GitHub 限制，需要排除"
→ 加入 .gitignore，重新提交推送
→ ✅ 成功

场景5：日常更新时新增大文件

用户：推一下

→ 扫描变更...发现新增文件：
  - demo.pptx (25MB)
→ "这个文件 25MB，确认要推吗？"
→ 用户确认排除 → 加入 .gitignore
→ 推送成功
→ ✅ 完成

场景6：发版本但没有新变更

用户：打个 release

→ 当前没有未提交的变更，直接进入版本发布
→ 当前最新 tag：v0.2.0
→ "建议 v0.3.0，可以吗？"
→ 用户自定义输入 v1.0.0
→ 生成变更摘要 + 创建 Release
→ ✅ Release v1.0.0 发布成功！

Files

Just SKILL.md in coding/git-push of yunshu0909/yunshu_skillshub.

Open the folder on GitHubat commit da0d31f

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in yunshu0909/yunshu_skillshub, which our catalogue first saw on October 7, 2026.

aiskillstore/marketplaceskills/yunshu0909/git-push

Compare with similar skills

Git Push 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 Push compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Git Push this skillyunshu0909/yunshu_skillshub	767	1 repos	~1.7k	Automated safety check: Notes	MIT	yesterday
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Release Bumpjamiepine/voicebox	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Creating Description For Gh PRredis/jedis	12k	—	~838	Automated safety check: Pass	MIT	today
Create Pull Request with Work Item IDmakeplane/plane	61k	—	~824	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
57k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Creating Description For Gh PR
redis/jedis
Official
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
12k GitHub stars~838 tokensUpdated today
DevelopmentAuto-check passed
Create Pull Request with Work Item ID
makeplane/plane
Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.
61k GitHub stars~824 tokensUpdated today
DevelopmentAuto-check passed
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
57k GitHub stars~2.5k tokensUpdated yesterday
DevelopmentAuto-check passed

More from yunshu0909/yunshu_skillshub

All 25 skills in this repo

Dual Agent Collaboration
yunshu0909/yunshu_skillshub
让 Codex 与 Claude Code 通过本机 CLI 组成“主执行者 + 独立审查者”的对称协作闭环。用于用户要求两个模型一起完成、交叉校核、独立审查、修到 ACK，或任务涉及产品需求收敛、复杂方案、跨模块开发、迁移、安全、重要重构和高质量交付时；无论从 Codex 还是 Claude Code 启动，都由当前模型主持，并完整调用另一方完成需求挑战、方案门禁、实现冷审和最终验收。
767 GitHub stars~2.2k tokensUpdated yesterday
Auto-check passed
Image Assistant
yunshu0909/yunshu_skillshub
配图助手 - 把文章/模块内容转成统一风格、少字高可读的 16:9 信息图提示词；先定“需要几张图+每张讲什么”，再压缩文案与隐喻，最后输出可直接复制的生图提示词并迭代。
767 GitHub starsUsed in 1 repo~536 tokens
Auto-check passed
Page Solution Design
yunshu0909/yunshu_skillshub
和用户一起敲定一个前端页面的整页方案（三层法：先定这页给用户什么，再定含哪几样怎么排，最后才是长什么样），最后打成一个定稿包（含高保真全状态与交互流程图）交给开发。触发：用户对一个页面说「想重做 / 重新设计 / 整页不对 / 太满 / 说不清具体改哪」，或「我们讨论一下这页怎么设计」。覆盖三种情形：① 已有页面整页重做；②「替换」——新方案占用同一个入口（同一路由 /…
767 GitHub stars~2.7k tokensUpdated yesterday
Auto-check passed
Backend Logic Design
yunshu0909/yunshu_skillshub
和用户一起把一个功能「看不见的部分」敲定：数据存哪、谁写谁读、怎么加载、怎么保存、默认值和升级、核心执行规则、出问题时怎么办、旧东西怎么迁。每条规则带编号、案例和状态（已定 / 方案里有但你没拍板 / 待你定 / AI 定），用户只回答带案例的新选择题、过目没拍过板的规则；给用户看的是按「你会问的问题」分组的问答卡片（最绕的逻辑配可点的模拟器）；最后请另一家模型只读查边界，问题闭环后封成后端逻辑…
767 GitHub stars~2k tokensUpdated yesterday
Auto-check passed
Article Study
yunshu0909/yunshu_skillshub
带用户精读一篇文章/文档并真正学透（不是出摘要）。五步：抽干货 → 切讲次 → 每讲跑「学-考-讲」循环 → 对号入座 → 实操+测验+讲错题+蒸馏。每讲产出 HTML 课件 + 笔记落盘；讲完必考一次，用户复述后必须挑不精确处拧紧；抽象概念上可交互演示（能点能跑）；全程用用户自己的业务场景当案例；学完出多题型自动判分测验卷，最后把收获蒸馏回用户的工具。核心触发条件是用户要的是"学会"而不是"要…
767 GitHub stars~964 tokensUpdated yesterday
Auto-check passed
Issue Pool
yunshu0909/yunshu_skillshub
Issue 池全生命周期管理（开发范式 v1 规划段）。核心是一条 issue 驱动的流程：用户随手丢想法，你把糊的 issue 变成能开工的 task——产出的是“问题定义”，不是“解决方案实现”；载体就是仓库根的 ISSUES.md。五个动作：记、并、拆、转、pending。规划规模只区分 single-task（一个版本能交付）与 roadmap（需要多批滚动），不得使用…
767 GitHub stars~996 tokensUpdated yesterday
Auto-check passed

Works with

Questions about Git Push

What does Git Push do?

When should I use Git Push?

Git Push fits situations like: tasks that involve Git workflow.

How do I install Git Push in Claude Code?

Run `npx skills add yunshu0909/yunshu_skillshub --skill git-push -a claude-code`. Or copy the skill folder (coding/git-push in yunshu0909/yunshu_skillshub) into .claude/skills/git-push in your project. Claude Code loads it when a task matches its description.

How do I install Git Push in Codex?

Run `npx skills add yunshu0909/yunshu_skillshub --skill git-push -a codex`. Or copy the skill folder (coding/git-push in yunshu0909/yunshu_skillshub) into .agents/skills/git-push in your project. Codex loads it when a task matches its description.

Can I use Git Push 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 yunshu0909/yunshu_skillshub --skill git-push -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-push, .gemini/skills/git-push, .github/skills/git-push and .opencode/skills/git-push in your project.

What does Git Push need to run?

Going by SKILL.md and its folder, Git Push needs the command-line tools its instructions call (git, gh and brew).

Does Git Push access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Git Push safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Git Push use?

Git Push is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Push use?

About 1.7k tokens (SKILL.md is roughly 6.8k 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 Push?

Skills that share tags, products or a category with Git Push: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Release Bump (jamiepine/voicebox, 57k stars) and Creating Description For Gh PR (redis/jedis, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Push?

yunshu0909 (a GitHub user) maintains it in yunshu0909/yunshu_skillshub, which has 767 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 6, 2026.

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

Install Git Push

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

一键推送 GitHub

功能说明

工作流程

第0步：环境检查 + 模式判断

第1步：项目扫描 + .gitignore 生成

1.1 扫描目录大小

1.2 敏感内容扫描（仅公开仓库）

1.3 生成或更新 .gitignore

第2步：用户决策

第3步：推送

3A. 首次推送（新项目）

3B. 日常更新（已有仓库）

推送失败处理

第4步：可选 — 版本发布（Release）

触发时机

流程

完成输出

核心原则

1. 扫描先于一切

2. 大文件主动拦截

3. 公开仓库双重检查

4. 不破坏已有内容

5. 每一步可中断

6. 日常更新要轻

使用示例

场景1：新项目首次推送

场景2：日常更新

场景3：发版本

场景4：推送时发现大文件

场景5：日常更新时新增大文件

场景6：发版本但没有新变更

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from yunshu0909/yunshu_skillshub

Related

Questions about Git Push