update-pr
Update an existing GitHub pull request title and description so they accurately describe the pull request as it exists now. Use when the user asks to update, rewrite, refresh, fix, or tighten a PR title/body, or when the PR scope has changed and the metadata needs to be brought back in sync.
Best for Maintaining PR clarity afte…Works with GitHubLow risk
⌘source
- author
@remix-run- repo
- remix-run/remix
- language
- TypeScript
★33kstars
2.8kforks
Apr 21, 2026
✦overview.md
Key Features
- ·Rewrites PR titles and descriptions from scratch
- ·Focuses on current net-new scope and behavior
- ·Synchronizes PR metadata with final code changes
- ·Uses GitHub CLI for updates
Use Cases
- →PR scope changed during development and metadata needs updating
- →Reviewers need clear summary of final feature/fix, not development history
- →PR title/body became outdated after multiple revisions
Best for
- ✓Maintaining PR clarity after scope changes
- ✓Teams with iterative development workflows
Not ideal for
- !PRs where development history documentation is required
- !One-time PR creation
FAQs
name
update-pr
description
Update an existing GitHub pull request title and description so they accurately describe the pull request as it exists now. Use when the user asks to update, rewrite, refresh, fix, or tighten a PR title/body, or when the PR scope has changed and the metadata needs to be brought back in sync.
Update PR
Overview
Rewrite pull request metadata as if drafting it from scratch for the current diff. Treat the title and body as a current reviewer-facing summary of the final net-new feature or bug fix in the PR, not as commentary about prior versions of the PR or the path taken to get there.
Workflow
- Read the current PR title/body and the current branch diff before drafting.
- Identify the PR's current net-new scope, APIs, behavior changes, and reviewer-relevant context.
- Rewrite the body from scratch so it describes the shipped feature/fix as it exists now.
- Review the title at the same time and update it whenever the body is updated.
- Apply the update with
gh pr edit.
Rules
- Never write the description as an update to itself. Do not say things like "this expands the original PR", "this PR now also", or similar process narration unless the user explicitly wants history called out.
- Describe the net-new feature or bug fix, not the implementation journey. Do not call out intermediate cleanup, refactors, rewrites, or iteration details unless they are necessary to understand the final delivered behavior.
$install
1-click copynpx skills add remix-run/remix --skill update-prSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.