skills.rest
gabrielkoerich
gabrielkoerichCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gh-pr-polish

Generate pull-request titles and bodies from Git history and changed files, then open PRs with gh CLI.

5|Updated Feb 4, 2026
Search Tags:#automation#git#pr#code-review#pull-request#gh-cli
One-click install
npx skills add https://github.com/gabrielkoerich/skills --skill gh-pr-polish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-pr-polish
Source: https://github.com/gabrielkoerich/skills/tree/main/gh-pr-polish
Command: npx skills add https://github.com/gabrielkoerich/skills --skill gh-pr-polish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Pull request descriptions often lack consistency and clarity; this skill generates high-signal PR titles and bodies from Git history and changed files, then opens PRs using the gh CLI.

Core Features & Use Cases

  • Generate cohesive PR titles and bodies from commits, diffs, and file changes.
  • Open PRs directly with gh using the generated content.
  • Use cases include standardizing PR messages across a repo and speeding up reviews by providing clear summaries.

Quick Start

Install and configure the skill, then generate PR content and create a PR using the provided scripts.

Frequently Asked Questions about gh-pr-polish

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

FAQPage Schema
How do I generate a pull request title and body from git commit history?▼

To generate a pull request title and body from git history, this skill analyzes your commits, diffs, and file changes to create high-signal PR descriptions. It then uses the gh CLI to automatically open the PR with that generated content.

Can I automatically open a pull request with gh CLI after generating the description?▼

Yes, you can automatically open a pull request with gh CLI. The skill generates cohesive PR titles and bodies from your changed files and git history, then directly executes gh commands to open the PR on your remote repository.

Do I need gh installed and authenticated to automate pull request creation?▼

Yes, you need gh installed and authenticated to automate pull request creation. The skill requires the gh CLI to open PRs and expects your current local branch to already be pushed to origin.

What is the best way to standardize PR descriptions across a repository?▼

The best way to standardize PR descriptions across a repository is to generate them directly from git history and changed files. This ensures consistent, high-signal messaging that speeds up code reviews and standardizes repository messaging.

Why does pull request automation require the current branch to be pushed to origin?▼

Pull request automation requires the current branch to be pushed to origin because the gh CLI needs an existing remote tracking branch to create the PR. The skill generates the PR content locally but relies on gh to push and open the remote pull request.

Related Skills

Explore More Software Engineering Skills→
hungthinh04hungthinh04

github-code-review

Review local git diffs and GitHub pull requests for code issues.

Community
Advanced
Cnext-euCnext-eu
1

SC-merge-pr

Merges a feature branch into main via automated gh CLI pull request.

Official
Intermediate
abhishekmmgnabhishekmmgn

ship

Orchestrate the end-to-end ship workflow from base-branch merge to PR creation.

Community
Advanced
helderbertohelderberto
114

open-pr

Open the current pull request in a browser using gh pr view --web.

Community
Advanced