菜单
Summarize the current pull request including diff, comments, and review status. Use when reviewing a PR, preparing for a review meeting, or getting a quick PR overview.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
| title | pr-summary |
| name | pr-summary |
| description | Summarize the current pull request including diff, comments, and review status. Use when reviewing a PR, preparing for a review meeting, or getting a quick PR overview. |
| context | fork |
| agent | Explore |
| allowed-tools | Bash(gh pr *) |
!gh pr view --json number,title,body,state,additions,deletions,changedFiles,reviews,statusCheckRollup
!gh pr diff --name-only
!gh pr view --comments 2>/dev/null | tail -50
Summarize this pull request:
From the PR title and body, describe what this pull request is trying to accomplish. Be specific — do not just restate the title.
From the changed files list and the additions/deletions counts:
From the comments section:
If there are no comments, say so.
Based on the review status and CI information from the JSON output:
Do not make a merge decision — only summarize the current state. The final merge decision belongs to the user.
