菜单
Script-first PR preparation with structured findings resolution, deterministic push safety, and explicit gate execution. USE WHEN readying a PR branch for merge after /review-pr, resolving review findings, or running pre-push gates and safety checks before pushing.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Sheshiyer/skill-clusters --skill prepare-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Arcplume runs Grok through the Grok Build CLI's own OAuth-authenticated session (grok login) for image generation, with strict preflight validation, secret-safe handling, and headless CLI-driven execution -- no separate XAI_API_KEY billing. Video falls back to the billed xAI API. USE WHEN a user wants to generate an image via a locally logged-in Grok Build CLI session, e.g. 'generate an image with grok', 'use grok build', or 'use my logged-in grok session'.
Shared reference for the Selemene cluster: the two report surfaces (deterministic Rust reports vs. narrative witness-pipeline readings), the @selemene/bridge CLI contract, the output manifest format, and non-prescriptive witnessing tone. USE WHEN deciding which Selemene surface to invoke or when routing between birth/compatibility/transit reports and solo/dyadic readings.
Route Selemene Engine tasks to the right surface: deterministic reports (birth/compatibility/transit) via selemene-core and the @selemene/bridge CLI, or narrative witness readings via selemene-report. USE WHEN the user wants anything under the Selemene/Noesis umbrella but has not named the exact surface.
基于 SOC 职业分类
正在显示 SKILL.md
| name | prepare-pr |
| description | Script-first PR preparation with structured findings resolution, deterministic push safety, and explicit gate execution. USE WHEN readying a PR branch for merge after /review-pr, resolving review findings, or running pre-push gates and safety checks before pushing. |
| cluster | git-pr-ops |
| version | 1.0.0 |
Prepare the PR head branch for merge after /review-pr.
.local/pr-meta.env if present in the PR worktree.main.--force-with-lease against known head SHA.git clean -fdx.scripts/pr-prepare init <PR>
.local/review.json is mandatory.BLOCKER and IMPORTANT items.Commit scoped changes with concise subjects (no PR number/thanks; those belong on the final merge/squash commit).
Run gates via wrapper.
Push via wrapper (includes pre-push remote verification, one automatic lease-retry path, and post-push API propagation retry).
Optional one-shot path:
scripts/pr-prepare run <PR>
scripts/pr-prepare init <PR>
ls -la .local/review.md .local/review.json .local/pr-meta.env .local/prep-context.env
jq . .local/review.json >/dev/null
List required items:
jq -r '.findings[] | select(.severity=="BLOCKER" or .severity=="IMPORTANT") | "- [\(.severity)] \(.id): \(.title) => \(.fix)"' .local/review.json
Fix all required findings. Keep scope tight.
jq -r '.changelog' .local/review.json
jq -r '.docs' .local/review.json
Use concise, action-oriented subject lines without PR numbers/thanks. The final merge/squash commit is the only place we include PR numbers and contributor thanks.
Use explicit file list:
scripts/committer "fix: <summary>" <file1> <file2> ...
scripts/pr-prepare gates <PR>
scripts/pr-prepare push <PR>
This push step includes:
.local/prep.env generation.ls -la .local/prep.md .local/prep.env
PR is ready for /merge-pr.gh pr merge in this skill.