菜单
Render and optionally publish a deterministic PR body from a validated verification bundle without changing its claims.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/carlitose/agent-skills --skill explain-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Drive a ticket folder AFK through deterministic scheduling, isolated implementation, evidence-backed quality gates, provider-neutral PRs, and explicit merge authorization.
Build and maintain a self-compiling markdown wiki — an Agent ingests raw sources and a project's own docs, compiles cross-linked concept/entity/source pages, builds a dated timeline from Git and session history, answers queries against the corpus, lints the graph for health, and applies human corrections filed in audit/. Use when (1) scaffolding a knowledge base for a research topic or a project's history, (2) ingesting articles/papers/notes into raw/sources/, (3) ingesting a repository's specs and tickets and building the temporal axis over them, (4) answering questions against the wiki and filing durable answers back, (5) running lint passes for dead links, orphan pages, index coverage, log and audit shape, (6) applying human feedback from audit/. Not for general note-taking, daily journals, or non-wiki Obsidian use.
Review a runner candidate or standalone PR, commit, local diff, or requested scope read-only for regressions, evidence gaps, and overclaims.
基于 SOC 职业分类
正在显示 SKILL.md
| name | explain-pr |
| description | Render and optionally publish a deterministic PR body from a validated verification bundle without changing its claims. |
Owns: PR-body rendering from an already validated bundle. It does not review code, reinterpret evidence, raise a claim ceiling, authorize merge, or decide integration.
The required sections, visibility rules, and wording ceiling come from the canonical Verification Record and its validator.
Require:
Reject missing/stale bundles. Never turn simulated, skipped, or gated evidence into a stronger narrative.
When invoked by ticket-autopilot, also require the runner's complete render-required
request. Preserve its render_request_hash and expected_head_sha literally; do not
recompute or substitute either identity.
Produce the headings required by the contract, including:
Use literal IDs and dispositions from the bundle so machines and reviewers can trace each statement. Do not add forbidden wording or infer provider capability.
Validate the rendered body with:
VERIFICATION_AUDIT_ROOT is the absolute verification-audit skill root resolved from the
skill catalog, never from repository cwd.
python3 -B "$VERIFICATION_AUDIT_ROOT/scripts/verification_contract.py" \
validate-pr <bundle.json> <body.md> --pr-head-sha <observed-sha>
If validation fails, fix rendering only. A semantic bundle problem goes back to
verification-audit; a changed head requires fresh upstream evidence.
When the user or scheduler requested publication, update only the PR body through the selected provider adapter, read it back, and revalidate the observed body/head. Return the body, validation result, provider observation, and any publication error. Never merge.
For the runner handoff, return render_request_hash, expected_head_sha,
rendered_body, the same validated verification_bundle, and the absolute
verification_audit_root. The runner, not this skill, persists content-addressed
artifacts, performs provider mutation/readback, and decides whether pr-open is reachable.