菜单
Automate PR creation and merging. Commits uncommitted changes, creates a PR targeting main, waits for CI/CD checks, and squash merges on success. Triggers on: ship it, ship this, create and merge pr, ship pr, merge to main.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Produces a bulletproof implementation plan for a GitHub issue by collaborating with three specialist subagents — senior engineer, application architect, and technical writer — in parallel, validating every claim against CONTEXT.md and the ADRs, then presenting the plan in plan mode for approval before any code is written. Every plan carries the full standard SDLC envelope (branch → implement → commit → CodeRabbit review + self-review → autofix → commit → PR → retro) so it lands a PR for sign-off and a concrete process improvement. Use when the user wants to plan or spec out a GitHub issue, runs /bulletproof-plan with an issue number or URL, or asks for a rigorous multi-specialist implementation plan.
Documents a target system (codebase, infra diagram, or verbal description) end-to-end as a nestable architecture graph through the infinite-docs MCP server — top-level Components, Connections, per-Component markdown, and nested interior Canvases. Use when the user wants to map, document, or capture a system's architecture into infinite-docs, mentions the infinite-docs MCP server, an architecture://-addressed resource, or an API token from a /connect page, or asks an agent to keep an architecture graph in sync with the system it describes.
Adds a new Component kind (`NodeKind` enum value) end-to-end — Prisma + Zod + parity guard + client catalog + server label + migration + docs + validation — in lockstep so the exhaustive `Record<NodeKind, …>` types catch any missing edit at compile time. Use when the user wants to "add a new component kind/type", "extend the NodeKind enum", "add X as a component kind", or names a specific new kind (`LAMBDA`, `BUCKET`, `WORKER`, etc.) to admit.
| name | ship-it |
| description | Automate PR creation and merging. Commits uncommitted changes, creates a PR targeting main, waits for CI/CD checks, and squash merges on success. Triggers on: ship it, ship this, create and merge pr, ship pr, merge to main. |
| user-invokable | true |
| compatibility | Requires gh CLI authenticated with repo permissions, and git |
Automate the full PR lifecycle: commit changes, create a PR, wait for CI/CD, and squash merge into main.
Follow each step sequentially. Stop and report to the user if any step fails.
Run these checks before anything else. If any fail, stop and tell the user why.
git branch --show-current. If in detached HEAD state, stop — tell the user to check out a named branch.git remote -v. If no remote is configured, stop — tell the user to add a remote.gh auth status. If not authenticated, stop — tell the user to run gh auth login.Save the current branch name for later use.
git status --porcelain to check for uncommitted changes (staged, unstaged, and untracked).main, skip to Step 3. If the working tree is clean and on main, stop — there is nothing to ship.git add <file1> <file2> ... with explicit file paths. Never use git add -A or git add ..git diff --cached --stat and git diff --cached to understand the changes.main, create a feature branch before committing (see Step 2b below).This step is called from Step 2.6 when the current branch is main. The branch must be created before the commit so that local main stays clean and avoids divergence after the PR is squash-merged.
feat/add-user-validation, fix/null-pointer-in-parser). Use kebab-case with a conventional prefix (feat/, fix/, chore/, refactor/, etc.).git checkout -b <branch-name> to create and switch to the new branch. Staged changes carry over to the new branch.git push -u origin HEAD to push the branch to the remote.gh pr view --json number,url 2>/dev/null.
git log main..HEAD --oneline.gh pr create --base main --title "<title>" --body "<body>".gh pr checks to get check status.gh pr merge --squash --delete-branch to squash merge and delete the remote branch.git checkout main.git pull origin main to get the merged changes.git branch -d <branch-name> (using the branch name saved in Step 1).main stays clean.gh.