Skip to content
Skills Library
Programming · Writing

pull-request:update

/pull-request: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.

Repository
claude ↗
Licence
MIT
Last repository change
23.10.2026

Assessment and security

80/ 100Class: good
Format15 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Arguments

/pull-request:update [pr-url | mr-url]
Original author 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.

How it works

  1. Arguments
  2. Context
  3. Workflow
  4. Writing
  5. GitLab Notes
Original SKILL.md headings · 42 lines, 313 words
SKILL.md preview
---
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/sem-context.ts --stack-file "${user_config.stack_file}"`

!`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/references/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.
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-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.

## GitLab Notes

For advanced GitLab features (username lookup), load `gitlab:merge-request`.

Versions

The database has no other skills named pull-request:update.

Database snapshot: 13.11.2026 · package version f43e660f5a40 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 92pr
    Use when writing a PR body.
  • 100update-pull-request
    Update an existing pull request's title and description to accurately reflect the implemented changes. Use this skill when asked to update, refresh, or rewrite a PR title or description, sync a PR with the latest changes, or when the PR description no longer matches the implementation.
  • 100write-pr
    Use when you write or materially update a pull request body. The body states the change, the evidence and the merge risk. It does not review or merge.
  • 100pr-description
    Use when writing or updating a pull request or merge request description for the current branch, for GitHub, GitLab, or Bitbucket.
  • 100pr
    Write or update a pull request body from the repo's PR template, with evidence and validation traced to commands actually run. Use when writing or updating a PR body. To open the PR itself, use file-pr.
  • 90pr
    Use when writing or updating a pull request description, or before running `gh pr create`.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.