update-pr

Reconcile incoming commits and publish updates to an existing pull request.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/aadorian/VSCode_Readme --skill update-pr-aadorian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/aadorian/VSCode_Readme/tree/main/education/sessions-chat-and-agents/sessions/skills/update-pr
Command: npx skills add https://github.com/aadorian/VSCode_Readme --skill update-pr-aadorian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you keep an existing pull request in sync with the latest branch state after new work, upstream updates, or review-driven fixes.

Core Features & Use Cases

  • Branch Reconciliation: Pulls in incoming PR commits when the remote has advanced beyond the current branch.
  • Validation and Repair: Runs compile and hygiene checks, then fixes issues before the pull request is updated.
  • PR Maintenance: Commits any remaining local changes and refreshes the pull request title and description when the scope has changed.
  • Use Case: You finished a follow-up fix after review and want the existing pull request updated cleanly without creating a new one.

Quick Start

Ask the skill to update the current pull request after you make local changes or need to merge in new incoming commits.

Frequently Asked Questions about update-pr

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

FAQPage Schema
How do I update an existing pull request with new commits after a code review?

To update an existing pull request, you need to reconcile incoming commits, resolve merge conflicts, and push fresh commits back to the same PR. This process folds your review follow-up fixes cleanly into the currently maintained branch.

What is the best way to sync my pull request branch with upstream changes?

Syncing a pull request branch requires pulling in incoming PR commits when the remote has advanced. You must perform branch merging and conflict resolution to align your local changes with the updated upstream state before refreshing the PR.

Can I refresh pull request metadata when the scope of my changes shifts?

Yes, you can refresh pull request metadata. When your change set shifts during active development, you can commit remaining local changes and update the pull request title and description to accurately reflect the new scope.

How do merge conflicts get handled when maintaining an active pull request?

Merge conflicts are handled through branch reconciliation during the pull request update. The process requires merging the advanced remote branch, resolving any conflicts locally, and ensuring the changes compile before creating fresh commits.

Does updating a pull request require running compile and hygiene checks?

Yes, updating a pull request involves validation and repair. The workflow runs compile and code hygiene checks, then automatically fixes identified issues before the fresh commits are published back to the pull request.

Why create new commits on an existing pull request instead of opening a new one?

Creating new commits on an existing pull request maintains a single continuous review thread. This approach cleanly folds local changes, upstream updates, and review follow-ups into one maintained PR without fragmenting the development history.