update-pr-from-branch

Generate PR titles and descriptions from git branch diffs.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/GeorgeSheppard/api.georgesheppard.dev --skill update-pr-from-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-pr-from-branch
Source: https://github.com/GeorgeSheppard/api.georgesheppard.dev/tree/main/.claude/skills/update-pr-from-branch
Command: npx skills add https://github.com/GeorgeSheppard/api.georgesheppard.dev --skill update-pr-from-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the generation of PR titles and descriptions from the current branch, reducing manual edits and speeding up code reviews.

Core Features & Use Cases

  • Analyzes diffs between the current branch and base to produce coherent PR titles and summaries.
  • Updates the associated PR on GitHub using MCP after user confirmation.
  • Provides an approval step to review and edit before applying changes.

Quick Start

Invoke the Claude Code command /update-pr-from-branch to generate and apply a PR title and description based on your current branch.

Frequently Asked Questions about update-pr-from-branch

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

FAQPage Schema
How do I automatically generate a PR title and description from a git branch?

You can automatically generate PR titles and descriptions from a branch by analyzing the git diff against the base branch. This process reads the code changes to produce coherent summaries and updates the associated GitHub PR via MCP after user confirmation.

Can I review and edit PR updates before they are applied to GitHub?

Yes, the PR update workflow includes an explicit approval step before applying changes. You can review and edit the generated PR titles and summaries to ensure accuracy before the updates are submitted to GitHub via MCP.

How does generating PR titles from branch changes help with code review?

Generating PR titles from branch changes automates the creation of coherent summaries from diffs, reducing manual edits. This speeds up code review by providing reviewers with accurate, automatically generated context about the branch modifications.

Do I need a GitHub MCP integration to update pull requests from a branch?

Yes, a GitHub MCP integration is required to update pull requests from a branch. The workflow relies on GitHub MCP to read branch diffs and apply the generated PR titles and descriptions directly to the repository after user approval.

What is the best way to update a pull request title based on current branch changes?

The best way to update a PR title from branch changes is to automate the diff analysis between the current branch and base. This generates a coherent title and summary, then updates the GitHub PR via MCP after you review and approve the previewed changes.