pr-describer

Generate pull request descriptions from git diffs or commit logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes clear, complete pull request descriptions from a git diff, commit log, or plain description of changes. Covers what changed, why, how to test it, and any risks or follow-ups. Use when user says "write a PR description", "write a PR for this", "PR description for these changes", "help me describe this PR", "write a pull request", or pastes a diff or list of commits without further instruction.

Core Features & Use Cases

  • Generate PR descriptions from a git diff, commit log, or plain description of changes.
  • Include what changed, why, how to test, and any risks or follow-ups.
  • Supports prompts like "write a PR description", "PR description for these changes", or pasting a diff or list of commits to produce a complete description.

Quick Start

Paste a git diff or commit log to generate a complete PR description.

Frequently Asked Questions about pr-describer

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

FAQPage Schema
How do I write a pull request description from a git diff?

To write a pull request description from a git diff, paste the diff or commit log into the tool. It parses the input to generate sections covering what changed, why, how to test, and potential risks or follow-ups.

What should a PR description include when documenting commit logs?

A PR description generated from commit logs should include what changed, why the modifications were made, how to test them, and any associated risks or follow-up tasks. This ensures comprehensive code review documentation.

Can I generate PR descriptions for multiple programming languages from change notes?

Yes, you can generate PR descriptions for multiple programming languages from plain change notes. The tool applies to code review workflows across Git repositories, parsing changes regardless of the specific language used.

What is the best way to document code review risks and follow-ups from a diff?

The best way to document code review risks and follow-ups from a diff is using an automated PR description generator. It parses diff inputs to explicitly produce sections detailing testing steps, risks, and necessary follow-up actions.

Do I need to provide a git diff to get a complete pull request description?

You do not strictly need to provide a git diff to get a complete pull request description. You can also input a commit log or a plain description of changes, and the tool will parse those to generate the comprehensive documentation.