pr-description-generator

Generate pull request descriptions from git diff and commit history.

1|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill pr-description-generator-pascallammers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-description-generator
Source: https://github.com/pascallammers/mylo-travel-concierge-v2/tree/main/.factory/skills/pr-description-generator
Command: npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill pr-description-generator-pascallammers

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of comprehensive and professional Pull Request (PR) descriptions, streamlining the code review process and improving communication.

Core Features & Use Cases

  • Automated Description Generation: Creates detailed PR descriptions based on git diff and commit history.
  • Standardized Template: Provides a consistent structure for PRs, including sections for What, Changes, Why, Testing, Screenshots, Breaking Changes, and related issues.
  • Use Case: When you've finished a feature and are ready to create a pull request, this skill can draft a complete description, saving you time and ensuring all necessary information is included for reviewers.

Quick Start

Use the pr-description-generator skill to draft a PR description for your current changes.

Frequently Asked Questions about pr-description-generator

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

FAQPage Schema
How do I generate a pull request description from git diff and commit history?

You can generate a pull request description by analyzing git diff and commit history to automatically create structured summaries of changes, rationale, testing procedures, and potential breaking changes for code review.

What should a professional PR description include for effective code review?

A professional PR description should include sections for what changed, the rationale, testing steps, screenshots, breaking changes, and related issues to facilitate a thorough and structured code review process.

Can I automate linking issues and generating testing steps in my pull requests?

Yes, you can automate linking issues and generating testing steps by analyzing code modifications from the git diff, ensuring reviewers have structured information and verifiable testing procedures.

Does the PR description generator work without external dependencies or specific platforms?

The PR description generator operates independently without external dependencies, using scripts and references to analyze your git history and produce standardized documentation for your pull requests.

What is the best way to standardize pull request templates across development teams?

The best way to standardize pull request templates is to automatically generate descriptions with a consistent structure covering what changed, why, testing, and breaking changes directly from your commit history.

When should I automate pull request documentation instead of writing it manually?

You should automate pull request documentation when you have finished a feature and are ready to create a pull request, saving time and ensuring all necessary information is included for reviewers.