skills.rest
Tyrizx
TyrizxOFFICIAL
Explore all skills by this author →
GitHub

update-pr

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

Updated Aug 30, 2026
Search Tags:#git#workflow#code review#pull request#commit#github#merge conflicts
One-click install
npx skills add https://github.com/Tyrizx/Tyrizx --skill update-pr-tyrizx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/Tyrizx/Tyrizx/tree/main/src/vs/sessions/skills/update-pr
Command: npx skills add https://github.com/Tyrizx/Tyrizx --skill update-pr-tyrizx

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 not yet present locally, 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 changes?▼

Invoke this Skill during a session with an open pull request. It pulls incoming commits, runs compile and hygiene checks, commits pending changes, and pushes the update with a revised title and description if needed.

How to handle merge conflicts when updating a pull request?▼

The Skill first checks for commits on the pull request that are missing locally, pulls them into the current branch, and resolves any merge conflicts before proceeding with validation and pushing.

Does the pull request description get updated automatically?▼

Yes, but only when the outgoing changes introduce significant modifications. In that case the Skill rewrites the pull request title and description to reflect the new state of the work.

What happens if there are uncommitted changes in my branch?▼

Uncommitted changes are committed using the /commit skill before the pull request is updated, ensuring nothing local is left out of the pushed commits.

When should I not use this pull request update workflow?▼

Avoid it when no pull request exists for the session, since it updates an existing PR rather than creating one. It is also unnecessary when there are no new commits or changes to push.

Related Skills

Explore More Software Engineering Skills→
ryoppippiryoppippi
256

pr-workflow-manager

Automate the pull request workflow from local changes to an opened PR.

Community
Intermediate
bitpantrybitpantry

finish-pr

Merge reviewed GitHub pull requests after tests pass and branches sync.

Community
Advanced
moltis-orgmoltis-org
2.8k

requesting-code-review

Run static security scans, baseline quality gates, and auto-fix loops before git commits.

Official
Advanced
axel-kaliffaxel-kaliff

integrate-main-branch-changes

Rebase a feature branch onto the latest origin/master with conflict guidance.

Community
Intermediate