Menu
Commit staged/unstaged changes with a well-crafted commit message.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Monitor CI checks after pushing, detect flaky vs legit failures, and auto-fix
End-of-day counterpart to wake-me-up. Reads today's morning briefing at ~/dev/ai/notes/wake-me-up/{date}.md, asks the user what they shipped or resolved, drafts a Slack wrap-up post in the user's voice, shows the draft for explicit confirmation, then posts it on the user's behalf via the Slack MCP. Appends the posted summary back to the briefing file so the file is a full day record. Use when the user says "/closing-time", "wrap the day", "end of day post", or wants help summarizing what they did.
Create or update a GitHub PR with automatic template detection and filling
Plan, implement, and iteratively review a task end-to-end using Claude + Copilot reviewers in a linear flow.
Investigate what it would take to upgrade a library from its currently pinned version to a target version (or "latest"). Produces a migration assessment — version delta, breaking changes that apply to us, impacted files, estimated blast radius, suggested rollout — and STOPS there. Does not perform the upgrade unless the user explicitly asks. Use when the user says "investigate updating <pkg> from X to Y", "investigate updating <pkg> to latest", "we are behind on <pkg>", or "let's update <pkg> to version N".
Shepherds a PR through the repetitive loop: run qa-swarm when there are substantive changes, triage qa-swarm findings, triage AI/bot review comments, keep the branch current with its base, watch CI, and apply the `stamphog` label once green. Use when the user says "/pr-shepherd", "shepherd this PR", "babysit this PR", or wants the whole review loop driven automatically. Accepts an optional PR number or URL as argument.
| name | commit |
| description | Commit staged/unstaged changes with a well-crafted commit message. |
| argument-hint | [--force] [<message hint>] |
| model | haiku |
Commit changes with a message that follows project conventions.
force = true if --force is present in the arguments.
message_hint = remaining text after stripping --force, or empty string if none was given.
Example invocations:
/commit/commit Fix race condition in job queue/commit Add webhook retry support/commit --force/commit --force Fix race condition in job queueRun in parallel:
git status # staged, unstaged, and untracked files
git diff HEAD # all uncommitted changes (staged + unstaged)
git log --oneline -10 # recent commits for message style reference
If git diff HEAD fails (no commits yet), run git diff --cached instead.
If git status shows a clean working tree with nothing staged, tell the user there is nothing to commit and stop.
Format:
<imperative subject line, ≤72 characters>
[optional body — include only when the subject alone does not tell a reader
why the change exists; omit entirely for small, obvious changes]
[Fixes #<issue> — include only when this commit closes a GitHub issue]
Subject line rules:
message_hint is non-empty, use it verbatim as the subject line (trim whitespace; do not rephrase)Attribution rules (non-negotiable):
If force is true, skip to Step 4 immediately — do not show a preview or ask for confirmation.
Otherwise, display the proposed commit exactly as shown below, then stop and wait for the user to reply:
Files to commit:
staged: <list, or "(none)">
unstaged: <list, or "(none)">
untracked: <list, or "(none)">
Commit message:
<subject line>
<body, if any>
<Fixes line, if any>
Ask: "Commit with this message? Reply yes to confirm, or describe any changes."
Do not proceed until the user replies. If the user requests changes, update the message and show the full preview again before asking once more.
Stage specific files by name. Do not use git add -A or git add ..
Use absolute paths in all bash commands.
git add <absolute path to each file>
git commit -m "$(cat <<'EOF'
<message>
EOF
)"
On success, show the short commit hash and subject line. On failure, show the full error output and stop.