pr-body

Name: pr-body
Availability: InStock
Author: Piece-Puzzly

Generate a GitHub pull request body from branch commits and a PR template.

Updated Aug 23, 2026

Search Tags:#automation #git #developer tools #code review #pull request #github

Ready to run

npx skills add https://github.com/Piece-Puzzly/Piece-iOS --skill pr-body

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-body
Source: https://github.com/Piece-Puzzly/Piece-iOS/tree/main/.claude/skills/pr-body
Command: npx skills add https://github.com/Piece-Puzzly/Piece-iOS --skill pr-body

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of Pull Request (PR) bodies by intelligently summarizing changes from your current branch, ensuring consistency and saving developers time.

Core Features & Use Cases

Automated PR Body Generation: Creates PR bodies based on commit history and repository PR templates.
Template Adherence: Ensures PRs follow the established structure defined in .github/pull_request_template.md.
Change Summarization: Extracts and formats ticket numbers, key changes, and notes from commit data.
Use Case: After completing a feature, run this Skill to generate a draft PR body that includes a ticket number, a summary of your commits, and placeholders for screenshots, ready for review.

Quick Start

Use the pr-body skill to generate a draft PR body for the current branch.

Frequently Asked Questions about pr-body

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

FAQPage Schema

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

Generate a pull request body from git commits by analyzing your current branch against a base branch, extracting ticket numbers, and summarizing changes into a predefined PR template for GitHub.

Can I use my existing GitHub PR template for automated PR body generation?▼

Automated PR body generation populates your existing GitHub PR template found in `.github/pull_request_template.md`, ensuring the drafted output adheres to your repository's established PR structure and formatting.

What is the best way to format commit history into a structured GitHub PR description?▼

Formatting commit history into a GitHub PR description is best handled by extracting ticket numbers, summarizing key changes from current branch commits, and mapping them directly into your repository's predefined PR template.

Does this automated PR body generation work if my base branch or PR template is missing?▼

Automated PR body generation handles edge cases including missing PR templates and base branch resolution, ensuring the commit summarization process completes and outputs a draft even without strict repository configurations.

How do I extract ticket numbers and change summaries from commits for a code review?▼

Extract ticket numbers and change summaries for code review by analyzing current branch commits against a base branch, automatically identifying ticket references and formatting key changes into a ready-to-use PR body.

Can I push the generated PR body directly to GitHub after commit summarization?▼

Direct push to GitHub after commit summarization requires user approval, handling the operation as an edge case where the generated PR body can be applied after explicit consent during the generation process.