Agent Skills
› fcakyon/claude-codex-settings
› update-pr-summary
update-pr-summary
GitHub用于根据完整代码变更集更新 Pull Request 的标题和描述。通过获取 PR 信息、分析分支差异，生成简洁明了的摘要并应用更新，支持指定 PR 编号或 URL。
Trigger Scenarios
用户要求更新 PR 摘要
用户要求更新 PR 描述
用户要求重写 PR 正文
用户要求刷新 PR 标题和正文
显式调用 update-pr-summary
Install
npx skills add fcakyon/claude-codex-settings --skill update-pr-summary -g -y
SKILL.md
Frontmatter
{
"name": "update-pr-summary",
"description": "This skill should be used when user asks to \"update PR summary\", \"update PR description\", \"rewrite PR body\", \"refresh PR title and body\", or explicitly invokes \"update-pr-summary\"."
}
Update PR Summary
Update a PR title and description based on the complete changeset.
When explicitly invoked with extra text, treat that text as the PR number or URL.
Process
-
Fetch PR info
- Use
gh pr view <pr> --json title,body,baseRefName,headRefName.
- Use
-
Analyze the complete changeset
- Use
git diff <base-branch>...HEADto review all committed changes in the branch. - Ignore unstaged changes.
- Make the summary describe the full branch diff, not just the latest commit.
- Use
-
Generate the updated summary
- Follow the
create-prskill format for title and body. - Title: a short human headline, capital first letter, no
fix:orfeat:prefix. Lead with the outcome, punchy over exhaustive. - Body: open on why, then short scannable bullets (one point each). Lead with the most visual proof. A webpage, UI, or design change MUST carry before/after images in a two-column table, never text describing the change. See the
create-prskill for uploading them to a release. - Numbers win: put benchmarks, counts, speedups and comparisons in a markdown table.
- One read, one section, no headers. Plain words, no buzzwords.
- No test plans, file lists, or line links.
- Follow the
-
Apply the update
- Use
gh pr edit <pr> --title "..." --body "...".
- Use
Version History
- 9d0ce8b Current 2026-07-25 10:34
