pr-prepare

Generate Markdown pull request descriptions from git context with conventional titles.

1|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/ByronWilliamsCPA/rag-processor --skill pr-prepare-byronwilliamscpa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-prepare
Source: https://github.com/ByronWilliamsCPA/rag-processor/tree/main/.claude/skills/pr-prepare
Command: npx skills add https://github.com/ByronWilliamsCPA/rag-processor --skill pr-prepare-byronwilliamscpa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing comprehensive and standardized pull request descriptions can be tedious and inconsistent, leading to delayed reviews and misunderstandings. This Skill automates the generation of PR descriptions, ensuring all necessary information is included and follows project templates, so you can focus on coding.

Core Features & Use Cases

  • Contextual PR Analysis: Automatically analyzes changes between branches to identify modified components, purpose, and impact, providing a solid foundation for your PR.
  • Template-Driven Generation: Creates PR descriptions based on a predefined project template, including sections for summary, changes, impact, and testing, ensuring consistency across your team.
  • Conventional Title Suggestion: Proposes PR titles adhering to conventional commit standards, making your PRs easy to categorize and track.
  • Use Case: After completing a feature branch, use this Skill to automatically draft a detailed pull request description, saving you time and ensuring your PRs are clear, consistent, and ready for review, accelerating your development cycle.

Quick Start

Prepare a pull request description for my current branch.

Frequently Asked Questions about pr-prepare

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

FAQPage Schema
How do I automatically generate a pull request description from my git changes?

Pull request description generation analyzes your branch changes, identifies modified components, and produces a structured Markdown description with summary, changes, impact, and testing sections. This Skill automates the process by gathering git context and applying your project template, so you paste a complete, ready-to-merge PR description.

Can I use PR templates with automated description generation?

Yes. This Skill creates PR descriptions based on predefined project templates, ensuring consistency across your team. It structures output with standard sections—summary, changes, impact, testing, and notes—tailored to your template requirements.

What information does an automated PR description include?

Automated PR descriptions include a conventional-commit-style title, summary of changes, list of modified components, impact analysis, testing details, and additional notes. The Skill gathers git status, logs, and diffs to populate each section with relevant context.

How do conventional commit titles help with pull requests?

Conventional commit titles follow a standard format (e.g., feat:, fix:, docs:) that categorizes changes, improves PR tracking, and makes commit history scannable. This Skill suggests titles matching these standards, so your PRs integrate seamlessly with team workflows and automation tools.

Does this work for pull requests across different branches?

Yes. This Skill analyzes changes between branches to identify what was modified, why, and what impact those changes have. It works across any PR workflow where you need to document the delta between your feature branch and the target branch.

What's the fastest way to prepare a PR description for code review?

Complete your feature branch, then use this Skill to instantly draft a detailed pull request description from your git changes. No manual writing needed—output a structured, template-compliant description ready to paste, so reviews start faster and stay consistent.