pull-request-descriptor

Generate structured Pull Request descriptions from code diffs and commit messages.

Updated Nov 10, 2025
One-click install
npx skills add https://github.com/SwiftyJunnos/Claude-Code-with-TDD --skill pull-request-descriptor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pull-request-descriptor
Source: https://github.com/SwiftyJunnos/Claude-Code-with-TDD/tree/main/.claude/skills/pull-request-descriptor
Command: npx skills add https://github.com/SwiftyJunnos/Claude-Code-with-TDD --skill pull-request-descriptor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive and well-structured Pull Request descriptions, saving developers significant time and ensuring all necessary information is communicated to reviewers.

Core Features & Use Cases

  • Automated Analysis: Analyzes code diffs and commit messages to understand changes.
  • Template Selection: Automatically chooses the most appropriate PR template (feature, bugfix, refactor, etc.).
  • Structured Output: Generates markdown descriptions with clear sections for summary, changes, motivation, testing, and more.
  • Use Case: After completing a new feature, you can run this Skill to generate a detailed PR description that includes a summary of the changes, how it was tested, and links to related issues, ready to be submitted.

Quick Start

Use the pull-request-descriptor skill to generate a PR description for your current branch.

Frequently Asked Questions about pull-request-descriptor

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

FAQPage Schema
How do I create a structured PR description for a feature or bugfix?▼

Yes, the generated markdown descriptions are structured and ready for submission via the gh pr create command or directly pasting into the GitHub UI.

Can I use the generated PR description with the GitHub CLI or UI?▼

Yes, the generated markdown descriptions are structured and ready for submission via the gh pr create command or directly pasting into the GitHub UI.

What do I need to generate PR descriptions from code diffs?▼

To generate PR descriptions from code diffs, you need a local git repository with distinct branches containing commit messages and code changes for the tool to analyze.

Does automated PR template selection work for different types of code changes?▼

Automated PR template selection works by evaluating the nature of code changes and diffs to automatically choose the most appropriate template, whether it is a feature, bugfix, or refactor.