pr

Analyze commit history to generate pull request titles and bodies.

Updated Mar 15, 2026

Search Tags:#automation #git #workflow #commit #pr #code-review #pull-request

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes commit history to extract intent, changes, and rationale, transforming them into clear, PR-ready descriptions and metadata.

Core Features & Use Cases

Generate PR titles that reflect the change scope and impact.
Compose detailed PR bodies with change explanations, testing notes, and references.
Align PRs with project conventions and reviewer expectations across repositories.

Quick Start

Provide a repository's commit history and let the skill generate a PR draft ready for review.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I generate a pull request from existing git commits?▼

You can generate a pull request from existing commits by providing your repository's commit history. The skill analyzes the commits to craft a clear, ready-to-submit PR draft, extracting intent and rationale to produce titles and bodies without pushing new changes.

What is the best way to write a PR body that aligns with project conventions?▼

The best way to write a PR body aligned with project conventions is to use an automated skill that analyzes commit history to compose detailed descriptions. It aligns the generated change explanations and testing notes with reviewer expectations across repositories.

Can I automate PR title and body generation without adding new commits?▼

Yes, you can automate PR title and body generation without adding new commits. The skill works by analyzing existing commit history on your branch to extract change scope and impact, generating PR-ready metadata without introducing pushes or branch changes.

How does analyzing commit history improve code review preparation?▼

Analyzing commit history improves code review preparation by extracting intent, changes, and rationale from past commits. It transforms these details into actionable pull request descriptions and reviewer-facing rationale, ensuring the PR clearly communicates the scope and impact of the changes.

Does this PR generation workflow require any specific git branch configuration?▼

This PR generation workflow does not require specific branch configuration, but it applies to workflows where PRs are created from existing commits or branches. You simply provide the commit history, and no new commits, pushes, or branch changes are introduced during generation.