skills.rest
awinogradov
awinogradovCOMMUNITY
Explore all skills by this author →
GitHub

pr:update

Update pull request titles and descriptions from commit history.

5|3|Updated May 19, 2026
Search Tags:#code review#pull request#GitHub#PR automation#commit history
One-click install
npx skills add https://github.com/awinogradov/code-assistants --skill pr-update-awinogradov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr:update
Source: https://github.com/awinogradov/code-assistants/tree/main/claude-plugins/autopilot/skills/pr%3Aupdate
Command: npx skills add https://github.com/awinogradov/code-assistants --skill pr-update-awinogradov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the updating of pull request titles and descriptions based on the latest commits in the branch, ensuring that the PR accurately reflects the changes made.

Core Features & Use Cases

  • Automated PR Updates: Automatically update PR titles and descriptions to reflect new commits.
  • Customizable Flags: Use flags like --release-notes and --closes to add release notes or close related issues.
  • Use Case: After pushing new commits to a PR branch, this Skill will update the PR title and description to include the new changes.

Quick Start

Run the 'pr:update' command to automatically update the PR title and description with the latest commits.

Frequently Asked Questions about pr:update

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

FAQPage Schema
How do I automatically update a pull request title and description after pushing new commits?▼

To automatically update a pull request title and description, you can use a PR automation script that analyzes your latest branch commits and rewrites the PR metadata to accurately reflect the new code changes.

Can I automatically add release notes and close issues when updating a GitHub PR?▼

Yes, you can automatically add release notes and close related issues when updating a GitHub PR by using specific command-line flags like --release-notes and --closes during the PR update process.

Do I need the GitHub CLI installed to automate PR description updates from commit history?▼

Yes, you need the GitHub CLI (gh) installed and authenticated in your environment, as it provides the necessary API interface to read commit history and update pull request metadata on your repository.

What is the best way to keep a GitHub PR description synchronized with branch commits?▼

The best way to keep a GitHub PR description synchronized with branch commits is to run an automated PR update command that parses the commit history and rewrites the PR title and description to match the latest changes.

Why does my pull request title not match the latest commits pushed to my branch?▼

Your pull request title does not match the latest commits because GitHub does not automatically rewrite PR metadata when new code is pushed, requiring a PR update script to synchronize the title and description with the branch history.

Related Skills

Explore More Software Engineering Skills→
clinecline
65.9k

create-pull-request

Create GitHub pull requests with the GitHub CLI and repository templates.

Official
Intermediate
junhuajunhua

github-sdlc

Manage GitHub issues, projects, pull requests, releases, and branches.

Community
Advanced
jguadagnojguadagno
18

pr-guardrails

Enforce branch naming, PR formatting, and issue linkage in GitHub workflows.

Community
Basic
NITRR-OfficialNITRR-Official
4

pr-description-generator

Generate pull request titles and descriptions from commit history.

Official
Intermediate