update-pr

Updates an existing pull request with new commits and revised metadata.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill update-pr-basedgod55hjl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/src/vs/sessions/skills/update-pr
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill update-pr-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping an open pull request in sync with ongoing work requires manually pulling incoming changes, resolving conflicts, running checks, committing, and rewriting the PR title and description. This Skill automates that entire update cycle for the current session's pull request. ## Core Features & Use Cases - Incoming Change Sync: Detects commits on the pull request that are missing from the current branch, pulls them in, and resolves merge conflicts. - Build and Hygiene Validation: Runs compile and hygiene tasks and fixes any errors before pushing. - Automatic Commit and PR Refresh: Commits uncommitted changes via the /commit skill and updates the PR title and description when changes are significant. - Use Case: A reviewer left feedback and pushed commits to your PR. Invoke this Skill to merge their changes, verify the build, commit your fixes, and push an updated pull request with an accurate description. ## Quick Start Update the pull request for this session with my 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 an existing pull request with new commits?

Invoke the update-pr skill during your session. It pulls any incoming commits from the pull request, runs compile and hygiene checks, commits uncommitted changes, and pushes the updated branch to the pull request.

How to sync a pull request branch with incoming changes?

The skill checks whether the pull request contains commits not present on your current branch. If incoming changes exist, it pulls them into your branch and resolves any merge conflicts before continuing.

Does the pull request title and description update automatically?

Yes, but only when the outgoing changes introduce significant modifications to the pull request. In that case the skill rewrites the title and description to reflect the new content before pushing.

What happens if there are merge conflicts when updating a PR?

The skill pulls the incoming changes into the current branch and resolves any merge conflicts as part of the first step. After conflicts are resolved, it proceeds with compile and hygiene tasks before committing.

When should I not use the update-pr skill?

Avoid it when no pull request exists for the current session, since it relies on PR context appended to the prompt. For creating a brand-new pull request rather than updating one, use a PR creation workflow instead.