pr-body-style

Draft GitHub PR bodies that summarize code changes and validation steps.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill pr-body-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-body-style
Source: https://github.com/ChristopherAlphonse/calphonse-skills/tree/main/pr-body-style
Command: npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill pr-body-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft or update GitHub PR bodies to reflect the code changes and align with the user's preferred style.

Core Features & Use Cases

  • Draft PR bodies that summarize the change outcomes, validation steps, and key context in a concise, business-focused tone.
  • Preserve the repository's PR template headings and sections unless the user asks to modify them.
  • Validate against the actual diff to ensure accuracy and avoid misrepresentation in reviews.

Quick Start

Provide a concise PR body for the current change using your preferred style.

Frequently Asked Questions about pr-body-style

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

FAQPage Schema
How do I draft a pull request body that accurately reflects code changes?

Yes, PR body drafting tools can preserve your repository's existing PR template headings and sections while generating the content, ensuring the structure remains intact unless you explicitly request modifications to the template.

Can I generate a concise PR description while preserving repository templates?

Yes, PR body drafting tools can preserve your repository's existing PR template headings and sections while generating the content, ensuring the structure remains intact unless you explicitly request modifications to the template.

What's the best way to write a reviewer-friendly PR body for GitHub?

PR body generation tools enforce guardrails and style rules to avoid speculative benefits, ensuring the description sticks to verified outcomes from the diff and does not overstate the impact of the code changes.

Why should I avoid speculative benefits when writing pull request descriptions?

PR body generation tools enforce guardrails and style rules to avoid speculative benefits, ensuring the description sticks to verified outcomes from the diff and does not overstate the impact of the code changes.

Does PR body drafting work without additional dependencies or components?

Yes, PR body drafting operates without requiring additional dependencies or component installations, allowing you to generate or update GitHub pull request descriptions directly using your preferred style rules.