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.

Ir a la instalación

Repositorio: yofine/Mexus
Última actividad en el origen: 19 de abril de 2026 a las 16:53
Idioma detectado de SKILL.md: inglés
Estrellas: 86
Forks: 6

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

board

Use when showing a Web board for a Markdown-only Agent Team Mission without a Mexus server.

2026-05-18

roundtable

Use when opening a RoundTable proposal in the active Markdown-backed Agent Team Mission.

2026-05-18

run

Use when executing the next tasks from a Markdown-backed Agent Team kanban with Claude Code or Codex background Agents.

2026-05-18

Ver todos los de este repositorio

/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

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

/gh-push — Commit & Push

Parse arguments

Steps

Safety

/gh-push — Commit & Push

Parse arguments

Steps

Safety