skills.rest
royhenengel
royhenengelCOMMUNITY
Explore all skills by this author →
GitHub

pr

Generates pull requests with titles and bodies from git history and planning docs.

Updated Dec 22, 2025
Search Tags:#automation#git#developer tools#code review#pull request#github
One-click install
npx skills add https://github.com/royhenengel/Claude-Customizations --skill pr-royhenengel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/royhenengel/Claude-Customizations/tree/main/skills/Git/pr
Command: npx skills add https://github.com/royhenengel/Claude-Customizations --skill pr-royhenengel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating pull requests by automating the analysis of branch changes and generating well-structured PR content.

Core Features & Use Cases

  • Automated Branch Analysis: Gathers git status, log, and diff information for the current branch.
  • Contextual Information Gathering: Checks for planning documents to enrich PR descriptions.
  • PR Content Generation: Creates a PR title and body based on commit history and planning context.
  • Use Case: After completing a feature, use this skill to automatically generate a PR with a clear summary, categorized changes, and relevant links to planning documents.

Quick Start

Use the pr skill to create a pull request for the current branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation from git branch changes?▼

You can automate pull request creation by analyzing git branch state, commit history, and planning documentation to generate structured PR titles and bodies conforming to conventional commit standards.

How does automated code review analysis work for GitHub pull requests?▼

Automated code review analysis works by gathering git status, log, and diff information, then checking for planning documents to enrich the PR description with categorized changes and contextual links.

Can I create a draft pull request using developer tools for code review?▼

Yes, you can create a draft pull request using developer tools that analyze your current branch and commit history, providing post-creation status updates for your code review workflow.

What's the best way to generate conventional commit PR titles from git history?▼

The best way to generate conventional commit PR titles is by analyzing your git branch state and commit history, automatically producing structured titles that adhere to standard formatting rules.

Does the automated PR generation work without planning documents?▼

Yes, automated PR generation works without planning documents by analyzing git status and commit history, though checking for planning documents enriches the generated PR body with additional context.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
chicago-joechicago-joe

babysit

Monitor GitHub pull request checks, reviews, and CI status for merge readiness.

Community
Intermediate
spencerbeggsspencerbeggs

merge-prep

Squash git feature branch commits into one conventional commit for PR merging.

Community
Advanced
CamiloAndresGTRUniandesCamiloAndresGTRUniandes
19

github-pr

Generate GitHub Pull Requests with conventional titles and structured descriptions via gh CLI.

Community
Basic