write-pr-description

Generate structured pull request descriptions from diffs, commits, and issues.

10|2|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/eveld/claude --skill write-pr-description
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-pr-description
Source: https://github.com/eveld/claude/tree/main/skills/write-pr-description
Command: npx skills add https://github.com/eveld/claude --skill write-pr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps teams produce consistent, high-quality PR descriptions, reducing reviewer time and miscommunication.

Core Features & Use Cases

  • Template-driven PR descriptions with sections like Summary, What Changed, Why, and Related Issues.
  • Git-aware integration with PR tooling to auto-insert diffs and cross-reference tickets.
  • Use Case: When opening a PR, generate a clear, reviewer-friendly description from the change summary and test results.

Quick Start

Provide a concise PR description for the latest changes by asking for a structured summary in the standard template.

Frequently Asked Questions about write-pr-description

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

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

You can generate a pull request description automatically by analyzing your git commits and diffs. The tool creates a structured summary directly from your code changes, ensuring the PR description accurately reflects the latest updates.

What is the best way to structure a PR description for code review?

The best way to structure a PR description for code review is using a standard template with sections like Summary, What Changed, Why, and Related Issues. This consistency reduces reviewer time and prevents miscommunication.

Can I auto-fill related issues in my GitHub pull request description?

Yes, you can auto-fill related issues in your GitHub pull request description. The tool cross-references tickets and integrates with PR tooling to map your code changes to the corresponding related issues automatically.

Does this PR description generator work with standard git diffs?

Yes, this PR description generator works with standard git diffs. It integrates directly with your git tooling to read code changes and drafts the reviewer-friendly description based on the diff output and commit history.

Why should I use a template for pull request descriptions?

You should use a template for pull request descriptions to enforce standard sections like Summary and What Changed. This helps teams produce consistent, high-quality PR descriptions, reducing review time and miscommunication.