skills.rest
remix-run
remix-runOFFICIAL
Explore all skills by this author →
Website𝕏@remix_runGitHub

update-pr

Update a GitHub pull request's title and body to reflect its current diff.

33.3k|2.8k|Updated Oct 26, 2020
Search Tags:#github#metadata#pr#update#pull-request#title#body
One-click install
npx skills add https://github.com/remix-run/remix --skill update-pr-remix-run
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/remix-run/remix/tree/main/.agents/skills/update-pr
Command: npx skills add https://github.com/remix-run/remix --skill update-pr-remix-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain accurate PR metadata by rewriting the title and body to reflect the PR's current diffs, preventing reviewer confusion.

Core Features & Use Cases

  • Rewrites the PR title to summarize latest changes.
  • Updates the PR body to describe shipped features or fixes as of the current diff.
  • Handles feature and bugfix PRs across GitHub repositories, with guidance on when to run the update.

Quick Start

Provide the PR number or URL and let this skill rewrite the title and body to reflect the latest changes.

Frequently Asked Questions about update-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a GitHub pull request title and body to match the latest diff?▼

You can update a GitHub pull request title and body by parsing the latest diff and rewriting the metadata for reviewer clarity. This ensures the PR title and description accurately summarize the shipped features or fixes via a single gh pr edit operation.

When should I rewrite PR metadata to reflect the current code diff?▼

You should rewrite PR metadata when the PR scope changes, after receiving reviews, or when final changes differ from the initial summary. Updating the PR title and body prevents reviewer confusion by ensuring the description matches the actual code diff.

What is the best way to keep a pull request description in sync with code changes across repositories?▼

The best way to keep a pull request description in sync is to automatically parse the current diff and regenerate the PR body. This rewrites the title and description to accurately reflect the latest state of the code across any GitHub repository.

Does this PR update approach work with standard GitHub pull requests and the gh CLI?▼

Yes, this approach works with standard GitHub pull requests by applying changes with a single gh pr edit operation. It handles both feature and bugfix PRs across GitHub repositories, requiring only the PR number or URL to rewrite the title and body.

How do I fix an outdated pull request title after modifying the branch scope?▼

To fix an outdated pull request title after modifying the branch scope, parse the latest diff to generate a new summary. This rewrites the PR title and body to accurately describe the shipped features or fixes as of the current code changes.

Related Skills

Explore More Software Engineering Skills→
shopsysshopsys
349

pr-diff-fetcher

Fetch pull request diffs, metadata, and commit messages via GitHub CLI or API.

Official
Advanced
thisisryanswiftthisisryanswift
2

ce-pr-description

Generate a conventional-commit-style PR title and value-first body file.

Community
Advanced
toilahuonggtoilahuongg
10

git-pr

Generate pull request titles and markdown descriptions from Git branch differences.

Community
Intermediate
udecodeudecode
1.2k

drafting-pr

Create and update GitHub draft pull requests with conventional commits.

Official
Intermediate