/update
Update a pull request or merge request body to reflect the current state of changes. Use when a PR/MR has evolved through additional commits and the body needs to reflect what will be merged.
$ npx -y skills add bendrucker/claude --skill update --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/update
Context preview
The summary Claude sees to decide when to auto-load this skill.
Update a pull request or merge request body to reflect the current state of changes. Use when a PR/MR has evolved through additional commits and the body needs to reflect what will be merged.
SKILL.md
update.SKILL.mdname: pull-request:update
description: |
Update a pull request or merge request body to reflect the current state of changes.
Use when a PR/MR has evolved through additional commits and the body needs to reflect what will be merged.
argument-hint: "[pr-url | mr-url]"
allowed-tools:
- mcp__github
- "Bash(git remote get-url:*)"
- "Bash(gh pr:*)"
- "Bash(glab mr:*)"
- "Bash(bun ${CLAUDE_PLUGIN_ROOT}/scripts/*)"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/contributing.ts`
Workflow
1. **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`
1. **Fetch PR diff**:
- **GitHub**: `gh pr diff $0`
- **GitLab**: `glab mr diff $0`
1. Filter commits after `updatedAt` to identify new work since the body was last written.
Writing
1. Rewrite the PR body per [`sections.md`](../create/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. 2. 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 "$(cat tmp/pr-body-<branch>.md)"`
GitLab Notes
For advanced GitLab features (stacking, username lookup), load `gitlab:merge-request`.
Read more
name: pull-request:update
description: |
Update a pull request or merge request body to reflect the current state of changes.
Use when a PR/MR has evolved through additional commits and the body needs to reflect what will be merged.
argument-hint: "[pr-url | mr-url]"
allowed-tools:
- mcp__github
- "Bash(git remote get-url:*)"
- "Bash(gh pr:*)"
- "Bash(glab mr:*)"
- "Bash(bun ${CLAUDE_PLUGIN_ROOT}/scripts/*)"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/contributing.ts`
Workflow
1. **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`
1. **Fetch PR diff**:
- **GitHub**: `gh pr diff $0`
- **GitLab**: `glab mr diff $0`
1. Filter commits after `updatedAt` to identify new work since the body was last written.
Writing
1. Rewrite the PR body per [`sections.md`](../create/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. 2. 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 "$(cat tmp/pr-body-<branch>.md)"`
GitLab Notes
For advanced GitLab features (stacking, username lookup), load `gitlab:merge-request`.
My personal plugin marketplace for Claude Code, Anthropic's AI coding assistant.
Repo: bendrucker/claude
Other skills on bendrucker-claude.
- /agent-ideas
Harvest agent-tooling ideas from prominent developers.
Open skill - /cleye
Type-safe CLI argument parsing with cleye, the standard parser for this repo's Bun scripts. Use when writing or editing any script that takes arguments (flags, positional parameters, subcommands, --help) instead of reading existing scripts for the pattern.
Open skill - /coverage
Measure Bun test coverage and close gaps on a specific file. Use when adding or editing tests, when asked about coverage, or when the PostToolUse coverage hook reports uncovered lines.
Open skill - /activity
Report real device usage from ActivityWatch. Covers per-app time, window titles, and active vs idle spans. Use when asked "what apps did I use", "how long was I in X", "what did I work on today", "how much was I active vs idle", or to mine usage patterns for automation.
Open skill - /history
Report shell history from atuin's local capture. Covers what commands ran, when, where, and how they exited. Use when asked "what commands did I run", "what was I working on in the terminal", "have I ever run X", "how do I usually invoke X", or about recent shell activity,
Open skill - /bun
Bun runtime patterns. Use when running bun commands, working with package.json/bun.lock, writing TypeScript scripts under Bun, or developing Claude Code plugins.
Open skill

