gh-push

Commit pending changes (optional) and push the current branch to the remote. Use when the user says "push", "push the code", "commit and push", or "send it up". Includes safety checks for main-branch pushes and force-push.

跳到安装

仓库: yofine/Mexus
最近来源活动: 2026年4月19日 16:53
检测到的 SKILL.md 语言: 英语
星标: 86
分支: 6

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/yofine/Mexus --skill gh-push

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

/gh-push — Commit & Push

Push the current branch to the remote, optionally committing staged/unstaged changes first. Arguments passed: $ARGUMENTS.

Parse arguments

force / -f → force-push (REQUIRES extra confirmation, see Safety below)

no-commit → skip the commit step, push existing commits only

message:"..." → use this commit message instead of drafting one

Any other text → treat as commit message body

Steps

Inspect state (run in parallel):

git status (no -uall)
git diff (unstaged)
git diff --staged
git branch --show-current
git log --oneline -5

Decide what to commit:

If there are no pending changes and no unpushed commits → nothing to do, tell the user.
If there are pending changes and no-commit was NOT set → draft a commit.
If the user listed specific files in arguments, only stage those. Otherwise stage only files relevant to the described change — never git add -A blindly, to avoid pulling in secrets or unrelated work.
Show the user the file list and draft message, then confirm unless arguments already specified a message.

Commit (if applicable) using HEREDOC:

git commit -m "$(cat <<'EOF'
<subject>

<body if needed>

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
EOF
)"

Match the repo's commit-message style (check recent git log).

Push:

Default: git push (or git push -u origin <branch> if upstream not set)
Force-push: only if force was passed AND the branch is not main/master AND the user re-confirms in this turn.
NEVER --no-verify.

After push:

Show git status to confirm clean.
If a PR exists for the branch (gh pr view --json url,state), print its URL.
If no PR and the branch isn't main, suggest creating one (but don't do it unprompted).

Safety

Pushing to main/master directly: warn and confirm once before pushing.

Force-push to main/master: refuse unless the user explicitly says "force push main, I mean it."

If the pre-push hook fails, do NOT retry with --no-verify. Investigate, report, stop.

If git status shows an uncommitted .env / credentials* / *.pem in the staging candidates, flag it and ask before staging.

/gh-push — Commit & Push

Push the current branch to the remote, optionally committing staged/unstaged changes first. Arguments passed: $ARGUMENTS.

Parse arguments

force / -f → force-push (REQUIRES extra confirmation, see Safety below)

no-commit → skip the commit step, push existing commits only

message:"..." → use this commit message instead of drafting one

Any other text → treat as commit message body

Steps

Inspect state (run in parallel):

git status (no -uall)
git diff (unstaged)
git diff --staged
git branch --show-current
git log --oneline -5

Decide what to commit:

If there are no pending changes and no unpushed commits → nothing to do, tell the user.
If there are pending changes and no-commit was NOT set → draft a commit.
If the user listed specific files in arguments, only stage those. Otherwise stage only files relevant to the described change — never git add -A blindly, to avoid pulling in secrets or unrelated work.
Show the user the file list and draft message, then confirm unless arguments already specified a message.

Commit (if applicable) using HEREDOC:

git commit -m "$(cat <<'EOF'
<subject>

<body if needed>

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
EOF
)"

Match the repo's commit-message style (check recent git log).

Push:

Default: git push (or git push -u origin <branch> if upstream not set)
Force-push: only if force was passed AND the branch is not main/master AND the user re-confirms in this turn.
NEVER --no-verify.

After push:

Show git status to confirm clean.
If a PR exists for the branch (gh pr view --json url,state), print its URL.
If no PR and the branch isn't main, suggest creating one (but don't do it unprompted).

Safety

Pushing to main/master directly: warn and confirm once before pushing.

Force-push to main/master: refuse unless the user explicitly says "force push main, I mean it."

If the pre-push hook fails, do NOT retry with --no-verify. Investigate, report, stop.

If git status shows an uncommitted .env / credentials* / *.pem in the staging candidates, flag it and ask before staging.

name	gh-push
description	Commit pending changes (optional) and push the current branch to the remote. Use when the user says "push", "push the code", "commit and push", or "send it up". Includes safety checks for main-branch pushes and force-push.
user-invocable	true
allowed-tools	["Bash(git status)","Bash(git diff)","Bash(git log)","Bash(git branch)","Bash(git add)","Bash(git commit)","Bash(git push)","Bash(gh pr view)"]

name	gh-push
description	Commit pending changes (optional) and push the current branch to the remote. Use when the user says "push", "push the code", "commit and push", or "send it up". Includes safety checks for main-branch pushes and force-push.
user-invocable	true
allowed-tools	["Bash(git status)","Bash(git diff)","Bash(git log)","Bash(git branch)","Bash(git add)","Bash(git commit)","Bash(git push)","Bash(gh pr view)"]

gh-push

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

/gh-push — Commit & Push

Parse arguments

Steps

Safety

/gh-push — Commit & Push

Parse arguments

Steps

Safety