What is pull-request:update?

A workflow for rewriting a pull request or merge request description after new commits change the result. The description explains what will be merged and why, rather than listing the whole development history.

Use it to inspect the current request, compare recent commits and the diff, and update the request body with the final user-facing changes.

It keeps reviewers and teammates from relying on an outdated summary after the code has evolved.

pull-request:update — Skill for Claude Code by bendrucker/claude

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add bendrucker/claude

Claude Code

/plugin install pull-request

Made for: Claude Code.

Or install pull-request, the plugin that ships this one along with the rest of its 4 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bendrucker/claude/update/github.svg)](https://agentmods.dev/skills/bendrucker/claude/update)

Your own site

<a href="https://agentmods.dev/skills/bendrucker/claude/update"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/update/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bendrucker/claude/update"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 694 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.00694
Opus 5.5	$0.00017	$0.00278
Sonnet 5.5	$0.00008	$0.00139
Haiku 4.5	$0.00004	$0.00069

Measured 1mo ago against content hash 31783485b745, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pull-request:update scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/pull-request/skills/update/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Pull Request

The PR body documents what will happen when merged, not the journey. Don't echo review feedback. Only mention changes if the ultimate result is user-facing.

Arguments

$0 (optional): the PR/MR to update, given as a URL, number, or branch name. The Workflow passes it to gh pr view/glab mr view. Default: with no argument, the tools resolve the PR/MR from the current branch.

Context

Remote URL: !git remote get-url origin
PR Template: !bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-template.ts

!bun ${CLAUDE_PLUGIN_ROOT}/scripts/git-context.ts

!bun ${CLAUDE_PLUGIN_ROOT}/scripts/sem-context.ts

!bun ${CLAUDE_PLUGIN_ROOT}/scripts/contributing.ts

Workflow

Fetch PR context: Use $0 (if provided) as a PR identifier (number or branch name). Fetch the current PR:
- GitHub: gh pr view $0 --json title,body,updatedAt,commits
- GitLab: glab mr view $0
Fetch PR diff:
- GitHub: gh pr diff $0
- GitLab: glab mr diff $0
Filter commits after updatedAt to identify new work since the body was last written.

Writing

Rewrite the PR body per sections.md, the same rules the create skill follows. Load the writing skill for the full set of tropes to avoid. If a PR template is provided in context, preserve its structure. The Entities block in the context lists what changed at the function and class level, so use it to judge what the change did, but lead the body with intent and never reproduce the list.
Write the updated body to a temp file (e.g., tmp/pr-body-<branch>.md) and apply:
- GitHub: gh pr edit --body-file tmp/pr-body-<branch>.md
- GitLab: glab mr update --description-file tmp/pr-body-<branch>.md
- A screenshot or recording the new body references by local path uploads with it: --attach ./shot.png per file on gh pr edit (load github:attach), or project uploads per gitlab:api pasted in before the update. Assets already in the body keep their uploaded URLs.

Read the full file on GitHub · 56 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · +2 lines 31783485b745
1mo ago First seen · 54 lines · 42 tokens per session scan A 475e94b12bee

Subscribe to this mod's changes

pull-request:update is a skill published in the GitHub repository bendrucker/claude (18 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 694 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Claude Code Commits Git and workflow Writing and docs claude-code-plugin

phx-pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 61 tokens

branch-and-worktree-workflow

Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…

cbrock84/headcount · 70 tokens

precommit

Pre-commit checks — lint:fix -> build -> test.

sd0xdev/sd0x-harness · 15 tokens

next-step

Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.

sd0xdev/sd0x-harness · 63 tokens

precommit-fast

Quick pre-commit checks — lint:fix -> test.