Menu
Commit, push, and create a PR in one shot — Boris Cherny's most-used daily command
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Full-lifecycle orchestration for comprehensive, no-compromise execution — roll-calls the right skills, fans out parallel/worktree agents, then closes the loop (verify, review, simplify, changelog, handoff, retro). Use when you want maximum effort, to go all-in, or to orchestrate a big task end-to-end.
Runs a short retrospective that PROPOSES edits to the user's Claude Code skills — capturing a newly-found gotcha, fixing a description that didn't auto-trigger, retiring a dead skill, or extracting a reusable pattern into a new skill. Improves the TOOLSET, not the session log. Use when the user signals satisfaction at the end of real work ("thanks", "thanks that worked", "that worked great", "nice", "perfect", "exactly what I needed"), or when they explicitly run /session-retro. Always proposes and waits for confirmation — never edits skills silently. In unattended runs (/orchestrate, overnight, or /session-retro --auto), writes proposals to ~/.claude/retro-proposals/ instead of blocking.
Generate a concise session handoff for resuming work later, including current state, decisions, open issues, and next steps.
Deep task decomposition into parallel workstreams with self-contained agent prompts. Use when you want to review the execution plan before committing to it.
Generate a handoff note for clean session transitions — preserves context across /clear or new sessions. Use when ending a session, when context is getting high, or when the user says "hand off", "wrap up the session", or "save state for next time".
Inspect and clean stale branches across multiple repositories using the dotfiles git-hygiene + gh-bootstrap toolchain. Use when the user asks about branch state, stale local branches, or "no ref was fetched" errors.
| name | commit-push-pr |
| description | Commit, push, and create a PR in one shot — Boris Cherny's most-used daily command |
| disable-model-invocation | true |
Commit, push, and create a PR for the current work. $ARGUMENTS
git status and git diff --staged to understand current stategit add -A — be specific, skip secrets and generated files)type: short description) based on the actual changes~/.claude/scripts/codex-review-gate.sh (or claude/scripts/codex-review-gate.sh in this repo). Run it after the commit, before the push, so it reviews the committed delta vs the base branch (exactly the PR contents) and ignores any unrelated WIP still in the tree. This is the concrete ADR-0003 stop-gate.
CODEX_GATE_REQUIRED=1 if this change must not ship un-reviewed.~/.claude/scripts/antigravity-review-gate.sh (or claude/scripts/antigravity-review-gate.sh in this repo). Run it after the Codex gate, before the push. This is the Gemini sibling of step 6 — a different model family, biased toward front-end / runtime / boundary-condition issues. It is advisory, not authoritative: the merge gate stays Codex (step 6) + CI (ADR-0003).
gh pr create:
gh pr checks <url> (it may still be pending — note that). If any check fails, surface the failure summary. The merge gate is Codex review (step 6) + CI green (see ADR-0003); Antigravity (step 7) is advisory. The Codex GitHub bot (chatgpt-codex-connector[bot]) reviews the PR asynchronously after it opens — the warn-only pre-merge hook (PreMergeCodexHarvest) captures its comments as deduped issues when you run gh pr merge, and (once wired) the nightly-docs-steward backstop catches any that land after the session — so you don't need to wait on them here; just confirm CI is healthy or flag what's red.