メニュー
Merge the current PR with branch deletion, but only after CI passes. Use when the user clearly means "merge the open PR" (e.g. plain "merge", "merge it", "ship it"). Do NOT use for git branch merges ("merge main into X") or code merges.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run the same comprehensive review your CI runs on PRs, but locally against your full local-vs-remote diff and printed as text in the session, with an optional fix loop. Use when the user wants to mirror or preview the CI code review before pushing, get their branch CI-clean, or run an iterative review-then-fix loop. Triggers on "run the CI review locally", "preview the CI review", "mirror CI", "ci review", "will CI pass", "review-and-fix before pushing". For a plain read-only local review with no CI-parity framing or fix loop, prefer /review-local instead.
For coding/implementation tasks, use your own judgement to delegate the actual code-writing to a subagent running an appropriately lower-power model, to conserve top-tier tokens. Triggers whenever a task is primarily writing or editing code (features, fixes, refactors, mechanical edits). Skip for judgement-heavy work (design, debugging, auditing, synthesis).
Inspect Claude Code session logs (transcripts) for the current or another project. Use when the user explicitly asks to "look at the claude logs", "parse my session", "what did I ask claude", "show the transcript", "list claude sessions", or similar phrasings referencing Claude's own JSONL logs.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Docs-aware grilling. Explores the repo's existing docs first, then interviews the user relentlessly about a plan or design while cross-referencing those docs and the code. Use when user wants to stress-test a plan against the project's existing documentation, says "grill me with docs", "grill against the docs", or similar.
Read the most recent screenshot(s) the user took. Use when the user references "the screenshot I took", "my latest screenshot", "look at the screenshot", "the 3 screenshots I just took", "a few screenshots", or similar phrasings that imply opening their most recent screen capture(s) without specifying a path.
| name | merge |
| description | Merge the current PR with branch deletion, but only after CI passes. Use when the user clearly means "merge the open PR" (e.g. plain "merge", "merge it", "ship it"). Do NOT use for git branch merges ("merge main into X") or code merges. |
First, confirm intent. Only proceed with this skill if it's obvious the user means "merge the current open PR." If they mean a git branch merge (e.g. "merge main into our branch") or a code merge (combining functions, files, etc.), stop and handle what they actually asked for instead.
If a PR merge is intended, follow these steps:
Get the current PR number using gh pr view --json number -q .number
Wait for CI to finish using gh pr checks <number> --watch > /dev/null && gh pr checks <number> — the first call blocks until checks complete (discarding its noisy per-refresh output), and the second produces one clean final-state block. Use a generous timeout on the Bash call.
Based on the final result:
If CI passed: Execute gh pr merge --merge --delete-branch to merge with a merge commit and delete both local and remote branches
When run from a local checkout of the PR branch, --delete-branch also switches the working copy back to the default branch, pulls the latest main, and deletes the local branch automatically. This is expected — do NOT tell the user to manually run git checkout main && git pull or git branch -d <branch> afterward; gh has already done it.
Report the final status to the user
