update-pr

Update GitHub pull request titles and bodies with branch commits.

8|Updated Jul 7, 2017
One-click install
npx skills add https://github.com/ebkn/dotfiles --skill update-pr-ebkn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/ebkn/dotfiles/tree/main/root/.claude/skills/update-pr
Command: npx skills add https://github.com/ebkn/dotfiles --skill update-pr-ebkn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious and error-prone process of updating an existing GitHub pull request after new commits are added to the branch, ensuring the PR title and body reflect recent changes while preserving any repository PR template and language conventions.

Core Features & Use Cases

  • Detects branch and repository state: identifies current branch, uncommitted changes, and whether commits are unpushed.
  • Respects PR templates and language: reads template files when present and fills sections while preserving headings and HTML comments.
  • Language- and convention-aware titles: drafts Conventional Commit-style titles, infers or honors template language, and avoids altering type(scope) tokens.
  • Safe update workflow: confirms missing PRs, asks about uncommitted changes, shows full proposed title/body for user approval, and pushes/edits only when appropriate.

Quick Start

Update the open pull request for the current branch with the latest commits, draft a conventional-commit style title and a template-preserving body, confirm the changes, and push the branch.

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 after pushing new commits to a branch?

You can update a pull request by detecting unpushed commits, drafting a Conventional Commit-style title, filling existing PR template sections, and invoking git and gh CLI commands to push the branch and edit the PR metadata for user approval.

Can I automatically generate Conventional Commit titles for my pull requests?

Yes, generating Conventional Commit titles for pull requests is possible by detecting branch state, inferring template language, and drafting titles that preserve type(scope) tokens without altering existing conventions.

How do I preserve a GitHub PR template when updating a pull request body?

Preserving a GitHub PR template involves reading template files when present and filling sections while maintaining original headings and HTML comments, ensuring the PR body stays structurally intact during updates.

Does this PR update workflow handle uncommitted changes before pushing?

Yes, this PR update workflow handles uncommitted changes by detecting current branch state, asking about uncommitted modifications, and showing the full proposed title and body for user approval before pushing any branch commits or editing the PR.

What is the safest way to edit a pull request title and body using gh CLI?

The safest way to edit a pull request using gh CLI is a workflow that confirms missing PRs, detects unpushed commits, shows the full proposed title and body for user approval, and invokes git and gh CLI commands to push and edit only when appropriate.

Why does my pull request title not match my latest branch commits?

Your pull request title may not match your latest branch commits because the PR metadata is unsynchronized. Drafting a language-aware Conventional Commit-style title and invoking gh CLI commands to edit the PR ensures the metadata reflects recent branch changes.