commit-push-pr

스타2

포크1

업데이트2026년 7월 9일 05:06

Commit, push, and create a PR in one shot — Boris Cherny's most-used daily command

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

jckeen

jckeen/dotfiles

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 개발자컴퓨터 및 수학직·SOC 15-1252

SKILL.md

readonly

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

Run git status and git diff --staged to understand current state
If there are unstaged changes, stage the relevant files (not git add -A — be specific, skip secrets and generated files)
Run the project's build/test/lint command if one exists. If it fails, fix it first
Write a conventional commit message (type: short description) based on the actual changes
Commit
Run the local Codex review gate — ~/.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.
- Exit 2 → STOP. Codex found critical/high/medium (P0–P2) issues. Surface them, fix them with a follow-up commit (or get an explicit override from the user), then re-run the gate. Do not push past a blocking review.
- Exit 0 → clean, or only low (P3+) findings — which the gate has already filed as GitHub issues so they're tracked. Proceed.
- Exit 3 / loud warning → Codex couldn't run (not installed/authed, offline). The gate degrades open; note it and continue, or set CODEX_GATE_REQUIRED=1 if this change must not ship un-reviewed.
Run the Antigravity (Gemini) gate — advisory second opinion — ~/.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).
- Exit 2 → Antigravity flagged blocking issues. Surface them. Fix if they're real; if you and the user judge them false positives or out of scope, note that and proceed — do not treat this as a hard stop the way step 6 is.
- Exit 0 / 3 → clean, only nits, or agy couldn't run (degrades open). Note and proceed.
- Skip this step for changes with no runtime/front-end surface (pure docs, config) where a second review adds no signal and only burns plan quota.
Push to the current branch (create remote tracking branch if needed)
Create a PR with gh pr create:
- Title: concise, under 70 characters
- Body: what changed, why, how it was tested
- Link any related issues with "Fixes #N" or "Relates to #N"
Output the PR URL
Check CI status with 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.

이 저장소의 다른 Skills

같은 저장소

orchestrate

jckeen/dotfiles

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.

2026-07-102

session-retro

jckeen/dotfiles

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.

2026-07-102

handoff

jckeen/dotfiles

Generate a concise session handoff for resuming work later, including current state, decisions, open issues, and next steps.

2026-07-102

decompose

jckeen/dotfiles

Deep task decomposition into parallel workstreams with self-contained agent prompts. Use when you want to review the execution plan before committing to it.

2026-07-102

handoff

jckeen/dotfiles

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".

2026-07-102

branch-hygiene

jckeen/dotfiles

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.

2026-07-092

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

Run git status and git diff --staged to understand current state
If there are unstaged changes, stage the relevant files (not git add -A — be specific, skip secrets and generated files)
Run the project's build/test/lint command if one exists. If it fails, fix it first
Write a conventional commit message (type: short description) based on the actual changes
Commit
Run the local Codex review gate — ~/.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.
- Exit 2 → STOP. Codex found critical/high/medium (P0–P2) issues. Surface them, fix them with a follow-up commit (or get an explicit override from the user), then re-run the gate. Do not push past a blocking review.
- Exit 0 → clean, or only low (P3+) findings — which the gate has already filed as GitHub issues so they're tracked. Proceed.
- Exit 3 / loud warning → Codex couldn't run (not installed/authed, offline). The gate degrades open; note it and continue, or set CODEX_GATE_REQUIRED=1 if this change must not ship un-reviewed.
Run the Antigravity (Gemini) gate — advisory second opinion — ~/.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).
- Exit 2 → Antigravity flagged blocking issues. Surface them. Fix if they're real; if you and the user judge them false positives or out of scope, note that and proceed — do not treat this as a hard stop the way step 6 is.
- Exit 0 / 3 → clean, only nits, or agy couldn't run (degrades open). Note and proceed.
- Skip this step for changes with no runtime/front-end surface (pure docs, config) where a second review adds no signal and only burns plan quota.
Push to the current branch (create remote tracking branch if needed)
Create a PR with gh pr create:
- Title: concise, under 70 characters
- Body: what changed, why, how it was tested
- Link any related issues with "Fixes #N" or "Relates to #N"
Output the PR URL
Check CI status with 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.