pr-update

Update an existing GitHub pull request's title and description from the final diff.

1|Updated Oct 18, 2025

Search Tags:#automation #git #github #diff #pull-request #pr-update

Ready to run

npx skills add https://github.com/furiosa-ai/agent_skills --skill pr-update

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-update
Source: https://github.com/furiosa-ai/agent_skills/tree/main/pr-update
Command: npx skills add https://github.com/furiosa-ai/agent_skills --skill pr-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refreshes pull request titles and descriptions to accurately reflect the latest commits by using the final diff as the source of truth.

Core Features & Use Cases

Open PR alignment: Detects an existing PR for the current branch and ensures its title and body match the latest changes.
Final-diff driven updates: Analyzes the current base..HEAD diff to generate a concise, accurate description.
Template-aware updating: Respects an existing PR template when present and prompts before overwriting manual edits.
Safe execution flow: Requires user confirmation before applying updates and explains changes prior to update.

Quick Start

Run the pr-update skill after pushing new commits to refresh your open pull request.

Frequently Asked Questions about pr-update

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

FAQPage Schema

How do I automatically update a GitHub pull request title and description after pushing new commits?▼

You can automatically update a GitHub pull request by analyzing the current base..HEAD diff to regenerate the title and description. This ensures the PR accurately reflects post-commit changes, rebases, or base-branch updates while respecting existing PR templates and requiring user confirmation before overwriting.

What is the best way to sync an open PR with the final diff after a rebase or base-branch change?▼

Syncing an open PR with the final diff after a rebase involves using the final diff as the source of truth to regenerate the description. The skill detects the existing PR for your current branch and updates its content to accurately reflect the latest changes, ensuring alignment without losing manual template edits.

Does updating a PR description overwrite my existing GitHub PR template?▼

Updating a PR description does not blindly overwrite your GitHub PR template. The skill is template-aware, respecting existing PR templates when present, and prompts for explicit user confirmation before overwriting any manual edits to ensure safe execution.

Can I update a pull request title from the terminal without manually editing the GitHub UI?▼

You can update a pull request title from the terminal by running the pr-update skill after pushing new commits. It detects the open PR for the current branch, generates a concise title from the final diff, and applies the update after explaining the changes and receiving your confirmation.

When do I need to regenerate a pull request description from a diff?▼

You need to regenerate a pull request description from a diff when the existing PR no longer reflects the latest commits, such as after post-commit updates, rebases, or base-branch changes. Using the final diff as the source of truth ensures the PR content accurately matches the latest code state.