skills.rest
funsaized
funsaizedCOMMUNITY
Explore all skills by this author →
Website𝕏@funsaizedGitHub

update-pr-summary

Update PR titles and descriptions from a complete branch diff.

1|1|Updated May 1, 2026
Search Tags:#git#github#pr#summary#update#pull-request
One-click install
npx skills add https://github.com/funsaized/claude-and-codex-settings --skill update-pr-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-pr-summary
Source: https://github.com/funsaized/claude-and-codex-settings/tree/main/plugins/github-dev/skills/update-pr-summary
Command: npx skills add https://github.com/funsaized/claude-and-codex-settings --skill update-pr-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates updating a PR's title and description to reflect the full changeset in the current branch, reducing manual rewrites and drift between code and PR metadata.

Core Features & Use Cases

  • Fetch PR info: Retrieve the PR's current title, body, base branch, and head branch using gh pr view <pr> --json title,body,baseRefName,headRefName.
  • Analyze the complete changeset: Compare the base branch with HEAD via git diff <base-branch>...HEAD to capture all changes, ignoring unstaged edits.
  • Generate and apply updates: Produce a clean, readable summary following the create-pr format, then apply it with gh pr edit <pr> --title "..." --body "...".
  • Handle extra context: When invoked with extra text, treat it as the PR number or URL to update the correct PR.

Quick Start

Provide the PR URL or number and ask to update its title and body.

Frequently Asked Questions about update-pr-summary

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

FAQPage Schema
How do I update a pull request title and description from branch changes?▼

To update a pull request title and description from branch changes, the skill retrieves current PR metadata via gh pr view, analyzes the complete git diff between the base branch and HEAD, and applies the generated summary using gh pr edit.

What is the best way to refresh PR metadata after pushing new commits?▼

Refreshing PR metadata after pushing new commits is handled by comparing the base branch with HEAD via git diff to capture all changes, then generating a clean, readable summary and applying it to the PR title and body with gh pr edit.

Can I update a GitHub PR summary using just the PR URL or number?▼

Yes, you can update a GitHub PR summary by providing the PR URL or number as input. The process treats this extra text as the target PR identifier to fetch metadata and apply the updated title and body.

Does updating a PR summary with git diff ignore unstaged edits?▼

Yes, updating a PR summary with git diff ignores unstaged edits because the analysis compares the base branch with HEAD using git diff <base-branch>...HEAD, capturing only committed changes in the complete changeset.

What format does the generated PR body follow when updating descriptions?▼

The generated PR body follows the create-pr format, producing a clean, readable summary that reflects the full changeset. This ensures consistency between the code modifications and the applied PR metadata.

Related Skills

Explore More Software Engineering Skills→
NVIDIANVIDIA
8.1k

review-github-pr

Summarize GitHub pull request diffs and identify key design decisions.

Official
Advanced
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
otomattyotomatty
3

create-pull-request

Create and update GitHub pull requests with automated checks and template descriptions.

Community
Advanced
sitharaj88sitharaj88
1

create-pr

Generate pull request titles, bodies, and test plans from staged changes.

Community
Intermediate