fill-pr-description

Generate GitHub pull request descriptions from commits, diffs, and templates.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/amandahla/agent-skills --skill fill-pr-description
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fill-pr-description
Source: https://github.com/amandahla/agent-skills/tree/main/skills/fill-pr-description
Command: npx skills add https://github.com/amandahla/agent-skills --skill fill-pr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts concise, technical pull request descriptions as GitHub Flavored Markdown from commits, diffs, and templates. When templates include Developer Verification Checklists, it aligns the checklist with the changes.

Core Features & Use Cases

  • Draft PR bodies from the latest commits, diffs, and repository templates
  • Aligns Type of Change with commit messages to ensure consistency
  • Supports existing PR templates by filling in sections and checklists

Quick Start

Provide a ready-to-paste PR description by analyzing the latest commits and repository templates.

Frequently Asked Questions about fill-pr-description

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

FAQPage Schema
How do I auto-generate a pull request description from commit history?

You can auto-generate a pull request description by translating your latest commits and diffs into ready-to-paste GitHub Flavored Markdown, aligning the type of change with your commit messages.

Can I automatically fill out existing GitHub PR templates from commit diffs?

Yes, existing GitHub PR templates are populated by analyzing your commit diffs and filling in repository-specific sections and Developer Verification Checklists automatically.

What's the best way to draft PR bodies for code review using commit messages?

Drafting PR bodies for code review is best handled by analyzing commit messages and diffs to produce concise, technical Markdown descriptions that align with your template's type-of-change sections.

Does PR description automation align the type of change with commit messages?

PR description automation aligns the type of change by parsing your commit messages and ensuring the generated pull request body accurately reflects the functional changes in the diff.

How do I populate a Developer Verification Checklist in a PR template from a diff?

You populate a Developer Verification Checklist by analyzing your commit diff, mapping the functional changes to the repository PR template, and aligning the checklist items with those updates.