菜单
Write GitHub pull request titles, descriptions, reviewer guidance, and validation notes in the repository's required format. Use when drafting a new PR body, revising an existing PR description, preparing reviewer guidance, or documenting checks and tests performed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Normalize an implementation brief, get explicit alignment, then execute, verify, and prepare the completed change for publication. Use when a proposed change needs approval before code edits, regardless of whether it came from an audit, review, spec, diagnosis, or user request.
Review live GitHub pull requests with delegated lanes, evidence validation, follow-up delta reviews, and GitHub inline or PR-level publishing. Use when asked to review a pull request, PR, GitHub PR, delegated review, parallel review, multi-agent review, subagent review, or follow-up PR review.
Run a structured code review (Codex default, Claude optional) as a closeout check on a local or PR branch before commit or ship.
Clean up a working implementation through repeated behavior-preserving review and fix rounds until no accepted cleanup findings remain. Use when a branch or worktree needs post-implementation cleanup, refactoring, de-duplication, dead-code removal, or ownership simplification without behavior changes.
Reviews codebase architecture from a system vantage point, including adjacent repos, cross-repo contracts, module depth, seams, test surfaces, and domain locality. Use when the user wants to improve architecture, find refactoring opportunities, simplify shallow modules, improve testability, or understand whether a repo-local cleanup is enough.
Diagnoses observable technical or operational issues from symptoms, logs, traces, failing commands, screenshots, telemetry, reports, code, config, or runtime state. Use when the user asks to investigate, debug, root-cause, or explain what is happening without implementing fixes.
| name | write-pull-request |
| description | Write GitHub pull request titles, descriptions, reviewer guidance, and validation notes in the repository's required format. Use when drafting a new PR body, revising an existing PR description, preparing reviewer guidance, or documenting checks and tests performed. |
## What was changed## How to review## What the implication was## Checks and tests performed## What was changed only when it adds useful review context.Describe the change concisely. For small PRs, a short paragraph is enough.
For bug fixes, add an Original symptom this addresses: block right after the summary when it helps reviewers understand the change.
Point reviewers to the relevant file, section, or commit order. Keep this proportional to the diff.
Describe the practical impact directly. Use Mermaid only when it materially improves understanding.
List only checks that add reviewer signal. Prefer:
pnpm run ci only when they add coverage beyond the default flowDo not restate obvious command behavior. If a routine command simply passed, say that directly.