pr-description-generator

Generate structured PR descriptions from project docs and git diffs.

4|1|Updated Feb 2, 2026

Search Tags:#automation #git #documentation #pull-request #dev-workflow #pr-description #code-changes

Ready to run

npx skills add https://github.com/dylpickledev/claude-analytics-framework --skill pr-description-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-description-generator
Source: https://github.com/dylpickledev/claude-analytics-framework/tree/main/.claude/skills/pr-description-generator
Command: npx skills add https://github.com/dylpickledev/claude-analytics-framework --skill pr-description-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generates high-quality, consistent PR descriptions based on project documentation and git changes, saving time and ensuring uniform communication.

Core Features & Use Cases

Reads project documentation (README.md, spec.md, context.md) and extracts goals, decisions, and scope.
Analyzes git changes to capture diffs, affected files, and impact, then composes a structured PR narrative.
Outputs a complete PR description with sections for Summary, Files Changed, Test Plan, Quality Checklist, and related issues.

Quick Start

Run the pr-description-generator on a PR context to automatically produce the PR description.

Frequently Asked Questions about pr-description-generator

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

FAQPage Schema

How do I automatically generate pull request descriptions from git changes?▼

Generate pull request descriptions automatically by reading project documentation like README.md and analyzing git diffs to output a structured narrative with summaries, changed files, and test plans. The tool extracts project goals and composes a complete PR description from the analyzed code changes.

Can I use project documentation like spec.md to write consistent PR descriptions?▼

Yes, you can use project documentation like spec.md to write consistent PR descriptions. The generator reads files such as context.md and spec.md to extract decisions and scope, ensuring the resulting PR description aligns with your project's documented goals and requirements.

What is the best way to structure a PR description for software engineering workflows?▼

The best way to structure a PR description is to include Summary, Files Changed, Test Plan, Quality Checklist, and related issues sections. This structured format ensures uniform communication and captures the full impact of code changes across software projects.

Does the PR description generator work for both new PRs and update PRs?▼

Yes, the PR description generator works for both new PRs and update PRs. It is applicable across software projects whenever a Git history exists alongside documentation, allowing it to capture diffs and affected files for any code modification.

Do I need specific documentation files to generate a PR description from code changes?▼

While having documentation files like README.md, spec.md, or context.md enhances the context, the generator analyzes git changes to capture diffs and affected files regardless. Project documentation is read to extract goals and decisions, improving the quality of the structured PR output.

Why should I automate PR documentation instead of writing it manually?▼

Automating PR documentation saves time and ensures uniform communication across software projects. Manually writing descriptions often leads to inconsistent formatting, whereas an automated generator reads project docs and git diffs to consistently output standardized sections like Test Plans and Quality Checklists.