pr

Create GitHub pull requests from the first commit differing from main.

Updated Jun 7, 2025

Search Tags:#automation #git #commit #github #branch #pr #pull-request

Ready to run

npx skills add https://github.com/erazemk/dotfiles --skill pr-erazemk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/erazemk/dotfiles/tree/main/agents/skills/pr
Command: npx skills add https://github.com/erazemk/dotfiles --skill pr-erazemk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams work on feature branches, PRs must have consistent titles and bodies derived from commits. This skill automates extracting the first commit that differs from main to form the PR title and composes the body from the commit messages, reducing manual drafting.

Core Features & Use Cases

Derives PR title from the first commit that differs from main.
Builds PR body from the corresponding commit description and messages.
Enforces a user-confirmation flow before pushing and creating the PR in GitHub.

Quick Start

Create a PR for the current branch using the first commit that differs from main as the title and body.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I automatically create a GitHub pull request title from a commit message?▼

Automating GitHub pull request creation derives the PR title directly from the first commit that differs from main, ensuring consistent metadata without manual drafting.

How do I generate a pull request body from git commit history?▼

Generating a pull request body from git commit history composes the description using the corresponding commit messages from your feature branch, reducing manual formatting effort.

Can I automate pull request creation without manually writing the title and body?▼

Yes, automating pull request creation extracts the first differing commit from main to populate both the title and body, enforcing a user-confirmation flow before pushing to GitHub.

Does the pull request automation workflow support drafting PRs before finalizing?▼

Yes, the pull request automation workflow supports drafting PRs as requested, enforcing a user-confirmation flow before pushing the branch and creating the PR in GitHub.

What is the best way to maintain consistent PR metadata across feature branches?▼

Maintaining consistent PR metadata across feature branches is best achieved by deriving titles and bodies automatically from the first commit that differs from main, standardizing the extraction process.

When should I not use automated commit-derived pull request titles?▼

Automated commit-derived pull request titles should not be used when your feature branch commits are not incremental or lack descriptive messages, as the PR metadata relies entirely on that first differing commit.