pr-formatting

Generate structured pull request descriptions from commits with testing and deployment notes.

Updated Oct 13, 2025

Search Tags:#automation #git #testing #deployment #pr #description #pull-request

Ready to run

npx skills add https://github.com/olioapps/claude-code-plugins --skill pr-formatting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-formatting
Source: https://github.com/olioapps/claude-code-plugins/tree/main/git-actions/skills/pr-formatting
Command: npx skills add https://github.com/olioapps/claude-code-plugins --skill pr-formatting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps automate the creation and updating of pull request descriptions, ensuring clarity, testing notes, and deployment considerations are included.

Core Features & Use Cases

Structured PR Descriptions: Generate clear summaries, changes, testing, and deployment notes.
Branch-to-PR Automation: Create draft PRs or update existing ones based on commits.
Repo Style Adaptation: Align descriptions with repository templates and guidelines.

Quick Start

Use the /git-actions:pr-write command to create a draft PR on your current branch, or /git-actions:pr-edit to update an existing PR.

Frequently Asked Questions about pr-formatting

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

FAQPage Schema

How do I automate pull request descriptions from my git commits?▼

Automate pull request descriptions by invoking /git-actions:pr-write to analyze commits on your current branch and generate structured content including changes, testing notes, and deployment considerations. The Skill creates draft PRs with comprehensive descriptions aligned to your repository's templates.

Can I update an existing pull request description automatically?▼

Yes, use /git-actions:pr-edit to update an existing PR description. The Skill analyzes your commits and regenerates the description with testing and deployment notes while respecting your repository's PR template guidelines.

What should a pull request description include for clarity and testing?▼

A clear PR description should summarize changes, document testing performed, note deployment considerations, and follow repository conventions. This Skill generates structured descriptions with all these elements to ensure reviewers have complete context for merging.

How do I ensure my PR descriptions follow repository templates and guidelines?▼

The Skill adapts descriptions to your repository's PR templates and style guidelines automatically. When you invoke /git-actions:pr-write or /git-actions:pr-edit, it analyzes commits and formats output to match your repo's conventions and required sections.

Does this work with draft pull requests before final submission?▼

Yes, the Skill follows a draft-first workflow. Use /git-actions:pr-write to create a draft PR with generated description and testing notes, review it, then finalize submission once you're satisfied with the structured content.

What git information does the Skill need to generate accurate PR descriptions?▼

The Skill requires access to your repository's commit history on the current branch, PR templates, and deployment guidelines. Invoking /git-actions:pr-write or /git-actions:pr-edit analyzes these inputs to generate comprehensive, structured descriptions.