update-pr

Update GitHub Pull Request titles and bodies via the GitHub CLI.

Updated Feb 29, 2020
One-click install
npx skills add https://github.com/kevinrobayna/dotfiles --skill update-pr-kevinrobayna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/kevinrobayna/dotfiles/tree/main/claude/dot-claude/skills/update-pr
Command: npx skills add https://github.com/kevinrobayna/dotfiles --skill update-pr-kevinrobayna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of updating GitHub Pull Requests by automatically generating clear, conventional commit-formatted titles and concise descriptions that emphasize the "why" behind the changes.

Core Features & Use Cases

  • Automated Title Generation: Creates PR titles following the conventional commits standard (<type>(<scope>): <description>).
  • Contextual Description Writing: Generates descriptions focusing on the motivation, trade-offs, and important decisions, rather than just restating code changes.
  • PR Identification: Can auto-detect the PR from the current branch or accept a PR number as input.
  • Use Case: After pushing changes for a new feature, use this Skill to ensure the PR has a professional and informative title and description, making it easier for reviewers to understand and approve.

Quick Start

Run /update-pr to refine the current pull request with an improved title and description.

Frequently Asked Questions about update-pr

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

FAQPage Schema
How do I automatically update a GitHub pull request title and description?

You can automatically update a GitHub pull request by running a command that analyzes the PR changes and programmatically rewrites the title and body. It uses the GitHub CLI to apply conventional commit-compliant titles and detailed contextual descriptions directly to the repository.

What is the conventional commits format for pull request titles?

The conventional commits format for PR titles follows the structure `<type>(<scope>): <description>`. This Skill generates and applies this format automatically to your existing GitHub pull requests to ensure standardized, professional communication of code changes.

Can I generate a PR description from code changes without manually writing it?

Yes, you can generate a PR description from code changes without manual writing. This Skill analyzes your pull request diffs and automatically writes a concise description focusing on the motivation, trade-offs, and important decisions rather than just restating the code modifications.

How do I update a GitHub PR from the current branch without finding the PR number?

You can update a GitHub PR from your current branch without finding the number by using the auto-detection feature. The Skill leverages the GitHub CLI to automatically identify the corresponding pull request from your active branch and updates its title and body.

Does this PR update tool require the GitHub CLI to modify pull requests?

Yes, this PR update tool requires the GitHub CLI (`gh`) to interact with repositories and modify pull requests. It depends on the CLI to programmatically push the generated conventional commit titles and contextual descriptions to the GitHub platform.

Why should I rewrite a pull request description after pushing code?

Rewriting a pull request description after pushing code clarifies the rationale and trade-offs behind the changes. This Skill refines the PR body to focus on the motivation, making it easier for reviewers to understand the context and approve the request.