git:20260724.ba82c82 to git:20261007.7a519d8

17 added, 23 removed. Audit A to A.

---

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

- 1. **Fetch PR info**

- - Use `gh pr view <pr> --json title,body,baseRefName,headRefName`.

- 2. **Analyze the complete changeset**

- - Use `git diff <base-branch>...HEAD` to review all committed changes in the branch.

- - Ignore unstaged changes.

- - Make the summary describe the full branch diff, not just the latest commit.

- 3. **Generate the updated summary**

- - Follow the `create-pr` skill format for title and body.

- - Title: a short human headline, capital first letter, no `fix:` or `feat:` 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-pr` skill 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.

+ 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.

- 4. **Apply the update**

- - Use `gh pr edit <pr> --title "..." --body "..."`.

+ 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>`.

+ 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.