fcakyon/claude-codex-settings / plugins/github-dev/skills/update-pr-summary
update-pr-summary
UnverifiedThis 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.
- 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>. - 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |