update-pr-summary
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".
Install
npx skills add https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/github-dev/skills/update-pr-summary
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install fcakyon-claude-codex-settings@llmmart
git clone https://github.com/fcakyon/claude-codex-settings.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole fcakyon/claude-codex-settings collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Update PR Summary
Update a PR title and body to describe the final change and evidence. Treat extra invocation text as the PR reference and any requested corrections. For issue title/body edits, use create-issue.
- Read repository guidance and fetch the current body before editing:
gh pr view <pr> --json title,body,baseRefName,headRefName,url. - Review the complete PR diff against its actual base, not this checkout's unrelated HEAD.
Use
git diff <remote>/<base>...<head>when those refs are current, otherwisegh pr diff <pr>. Ignore changes outside the PR and collect completed checks relevant to its current head. - Read create-pr for title, body, evidence, and visual-hosting guidance. Apply the user's correction to the relevant portion. Preserve uploaded visuals, bot-added context, links, and valid results. An explicit full rewrite still keeps those unless the user asks to remove them. Rewrite stale claims and titles around the final scope.
- Save the exact body to a temporary file outside the repo. Re-read the remote body just
before writing. If it changed, incorporate those edits rather than overwriting them.
Apply with
gh pr edit <pr> --title "..." --body-file <path>, adding--attach <path>(gh >= 2.99.0) for any new Before/After visuals or figures referenced inline in the body. - Read back
title,body,urland compare with the intended edit. Verify that preserved content, fences, tables, and links survived. Open the PR to check media rendering when relevant. Report the PR URL and any remaining evidence or upload gap.
Files (claude-codex-settings)
-
SKILL.md 1.8 KB
--- 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 body to describe the final change and evidence. Treat extra invocation text as the PR reference and any requested corrections. For issue title/body edits, use [create-issue](../create-issue/SKILL.md). 1. Read repository guidance and fetch the current body before editing: `gh pr view <pr> --json title,body,baseRefName,headRefName,url`. 2. Review the complete PR diff against its actual base, not this checkout's unrelated HEAD. Use `git diff <remote>/<base>...<head>` when those refs are current, otherwise `gh pr diff <pr>`. Ignore changes outside the PR and collect completed checks relevant to its current head. 3. Read [create-pr](../create-pr/SKILL.md) for title, body, evidence, and visual-hosting guidance. Apply the user's correction to the relevant portion. Preserve uploaded visuals, bot-added context, links, and valid results. An explicit full rewrite still keeps those unless the user asks to remove them. Rewrite stale claims and titles around the final scope. 4. Save the exact body to a temporary file outside the repo. Re-read the remote body just before writing. If it changed, incorporate those edits rather than overwriting them. Apply with `gh pr edit <pr> --title "..." --body-file <path>`, adding `--attach <path>` (`gh >= 2.99.0`) for any new Before/After visuals or figures referenced inline in the body. 5. Read back `title,body,url` and compare with the intended edit. Verify that preserved content, fences, tables, and links survived. Open the PR to check media rendering when relevant. Report the PR URL and any remaining evidence or upload gap.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.