pr-description-writer

Generate and verify GitHub pull request descriptions from git diffs and templates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/meriley/claude-code-skills --skill pr-description-writer-meriley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-description-writer
Source: https://github.com/meriley/claude-code-skills/tree/main/skills/pr-description-writer
Command: npx skills add https://github.com/meriley/claude-code-skills --skill pr-description-writer-meriley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that your GitHub pull request descriptions are accurate, complete, and free from fabricated claims or marketing jargon, saving you from potential misunderstandings and ensuring technical integrity.

Core Features & Use Cases

  • Automated Description Generation: Creates PR descriptions based on git changes and project templates.
  • Rigorous Verification: Audits descriptions against actual code changes, flagging any inaccuracies or unverified claims.
  • Use Case: When creating a pull request, this skill automatically generates a detailed description, analyzes the code changes, and verifies that every statement in the description is supported by the code, preventing the introduction of unverified features or performance claims.

Quick Start

Use the pr-description-writer skill to write a PR description for the current branch.

Frequently Asked Questions about pr-description-writer

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

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

To generate a GitHub pull request description, this Skill analyzes your current git diff and commit history to populate template sections like Summary, Changes, and Testing. It automatically drafts the description based on actual code modifications.

Can I automatically verify PR descriptions against actual code changes?

Yes, you can verify PR descriptions against actual code changes using this Skill's rigorous auditing feature. It enforces a zero-fabrication policy, critically checking all statements against the git diff and flagging any unverified claims.

How do I prevent marketing language and unverified performance metrics in pull request documentation?

To prevent marketing language and unverified metrics in pull request documentation, this Skill critically verifies all claims against actual code modifications. It automatically flags unsupported performance metrics and marketing jargon during generation.

Does PR description generation work without external dependencies?

Yes, PR description generation works without external dependencies. This Skill operates independently to analyze your git changes and project templates, requiring no additional modules to enforce its zero-fabrication verification policy.

What is the best way to ensure technical integrity in automated code review documentation?

The best way to ensure technical integrity in code review documentation is to use a generation tool that cross-references every claim with the actual git diff. This Skill enforces a zero-fabrication policy to prevent inaccuracies.

Why does my automated PR description contain fabricated features not present in the code?

Automated PR descriptions might contain fabricated features if the generation tool lacks rigorous verification. This Skill solves this by critically auditing all claims against actual code modifications and flagging any unsupported statements.