Menú
Stage all changes, commit with an auto-generated message, pull/rebase remote, and push.
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.
Basado en la clasificación ocupacional SOC
Stage all changes and commit with an auto-generated message. Does NOT push.
Distill the current session into a rich, scoped memory entry — for Codex sessions, append to ~/.codex/memories/rollout_summaries/ in the established task-group format; for Claude sessions, write to the auto-memory directory. Use when you've finished a non-trivial unit of work that future-you (or another agent) should benefit from.
Create a new pull request or update an existing one's title and description. Use when the user asks to open a PR, submit a PR, update a PR, or push changes for review.
Squash all local commits (ahead of remote) into a single commit with an auto-generated message.
Update peon-ping configuration — volume, pack rotation, categories, active pack, and other settings. Use when user wants to change peon-ping settings like volume, enable round-robin, add packs to rotation, toggle sound categories, or adjust any config.
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
| name | push |
| description | Stage all changes, commit with an auto-generated message, pull/rebase remote, and push. |
Gather context: Run git status --short, git diff --stat, git log --oneline -5, and git rev-parse --abbrev-ref HEAD.
Stage all changes: Run git add -A to stage everything (tracked and untracked).
Generate a commit message: Analyze the staged diff (git diff --cached) and recent commit history. Write a concise, conventional-commit-style message (e.g. feat:, fix:, refactor:, chore:, docs:). The first line must be under 72 characters. Add a body only if the change is non-trivial. If $ARGUMENTS is provided, use it as guidance for the commit message — but still write the message yourself.
Commit: Create the commit. Do NOT amend an existing commit. Do NOT use --no-verify.
Pull with rebase: Run git pull --rebase to fetch and rebase on top of the remote branch. If the current branch has no upstream, skip this step.
git rebase --continue. If a conflict is ambiguous or risky, abort the rebase (git rebase --abort) and report the issue to the user — do NOT force through.Push: Run git push. If the branch has no upstream, use git push -u origin HEAD.
Report the commit message, number of files changed, and whether the push succeeded.