How do I install the PR: Update skill?

Run npx skillmds@latest add jasonwarrenuk/pr-update in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the PR: Update skill do?

Update a PR description to account for commits made since it was last written It is listed under Coding & Dev Tools on SkillMD.

Is PR: Update safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with PR: Update?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is PR: Update free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published PR: Update?

JasonWarrenUK (@jasonwarrenuk) published this skill. Their other Agent Skills are listed on their SkillMD profile.

PR: Update by jasonwarrenuk — Agent Skill

Name: PR: Update
Rating: 4.666666666666667 (3 reviews)
Author: JasonWarrenUK

File contents

Update an Existing PR

Update the description of PR #$ARGUMENTS.

Steps

1. Gather the facts in one call

"$HOME"/.claude/library/scripts/pr-facts.sh $ARGUMENTS

It prints the PR metadata, the current body, the watermark (, or "none" when the whole branch is new), every commit since it with per-commit stats, and the SHA to use as the next watermark. Analyse that dump rather than running exploratory gh/git calls. Exit 3 means no new commits; tell me the description is already up to date and stop. Exit 2: report the script's message.

2. Analyse the new commits

From the dump, understand what changed and why. Group related commits into coherent change categories. Run git show <sha> on a specific commit only where the stat alone can't tell you what a change is.

3. Produce the updated PR body

Take the existing body (in the dump) and update it:

Do not rewrite from scratch. Preserve existing content unless it is now inaccurate.
The body structure follows ~/.claude/library/templates/pr-description.md (the same template pr-create fills); keep updates within that structure rather than adding new top-level sections.
Integrate, never append. Fold the new work into the existing sections: ## Changes gains or amends entries, summaries absorb the new scope, stale statements get corrected in place. Bolting an "updates since" block onto the end of the description is the failure mode this step exists to prevent: the reader must see one coherent current description, not a base version plus a changelog of patches.
Provenance lives in its own trail, not in the body content. Maintain a single collapsible block immediately above the watermark:
```
<details><summary>Update history</summary>

- 2026-08-13: folded in <one-line summary> (`<first-sha>..<last-sha>`)
</details>
```
Append one dated line per update run. This block records that and when the description changed; the substantive content itself always lands in the sections above.
If the description references behaviour that has changed, correct it.
Insert or replace the watermark comment at the very end of the body, using the next watermark sha from the dump:

<!-- pr-update-watermark: <latest-sha> -->

4. Show me the diff

Display the updated body in full and a brief summary of what changed vs the previous description. Wait for my approval.

5. Apply the update

Once approved: gh pr edit $ARGUMENTS --body "<updated body>". Confirm success.

---name: pr-updatedescription: Update a PR description to account for commits made since it was last written---# Update an Existing PRUpdate the description of PR #$ARGUMENTS.## Steps### 1. Gather the facts in one call```bash"$HOME"/.claude/library/scripts/pr-facts.sh $ARGUMENTS```It prints the PR metadata, the current body, the watermark (``, or "none" when the whole branch is new), every commit since it with per-commit stats, and the SHA to use as the next watermark. Analyse that dump rather than running exploratory `gh`/`git` calls. Exit **3** means no new commits; tell me the description is already up to date and stop. Exit **2**: report the script's message.### 2. Analyse the new commitsFrom the dump, understand what changed and why. Group related commits into coherent change categories. Run `git show <sha>` on a specific commit only where the stat alone can't tell you what a change is.### 3. Produce the updated PR bodyTake the existing body (in the dump) and update it:- **Do not rewrite from scratch.** Preserve existing content unless it is now inaccurate.- The body structure follows `~/.claude/library/templates/pr-description.md` (the same template `pr-create` fills); keep updates within that structure rather than adding new top-level sections.- **Integrate, never append.** Fold the new work into the existing sections: `## Changes` gains or amends entries, summaries absorb the new scope, stale statements get corrected in place. Bolting an "updates since" block onto the end of the description is the failure mode this step exists to prevent: the reader must see one coherent current description, not a base version plus a changelog of patches.- **Provenance lives in its own trail, not in the body content.** Maintain a single collapsible block immediately above the watermark: ```markdown <details><summary>Update history</summary> - 2026-08-13: folded in <one-line summary> (`<first-sha>..<last-sha>`) </details> ``` Append one dated line per update run. This block records *that* and *when* the description changed; the substantive content itself always lands in the sections above.- If the description references behaviour that has changed, correct it.- Insert or replace the watermark comment at the very end of the body, using the `next watermark sha` from the dump:```text```### 4. Show me the diffDisplay the updated body in full and a brief summary of what changed vs the previous description. **Wait for my approval.**### 5. Apply the updateOnce approved: `gh pr edit $ARGUMENTS --body "<updated body>"`. Confirm success.

Frequently asked questions

PR: Update