skills.rest
lvndry
lvndryCOMMUNITY
Explore all skills by this author →
GitHub

pr-description

Generate PR titles and descriptions from diffs and branch context.

47|8|Updated Sep 13, 2025
Search Tags:#automation#PR#generate#code-review#conventional-commits#git-diff
One-click install
npx skills add https://github.com/lvndry/jazz --skill pr-description-lvndry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/lvndry/jazz/tree/main/skills/pr-description
Command: npx skills add https://github.com/lvndry/jazz --skill pr-description-lvndry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates clear, structured pull request titles and descriptions directly from code changes and branch context, helping teams review and merge faster.

Core Features & Use Cases

  • Automated PR Title Drafting: Create concise, conventional-commit-style titles from diffs and scope.
  • Descriptive PR Summaries: Produce a summary of changes, rationale, and testing steps.
  • PR Governance: Enforce standard formats and link related issues for traceability.
  • Use Case: When a developer opens a PR after a feature branch, invoke this skill to auto-create a title and description that reflect the changes and linked issues.

Quick Start

  • Open a PR or start a merge request in your repo
  • Run the skill with the current branch to generate a title and description
  • Review and paste the generated content into your PR form

Frequently Asked Questions about pr-description

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

FAQPage Schema
How do I auto-generate a PR title and description from a git diff?▼

To auto-generate a PR title and description, you can use a skill that analyzes your git diff and branch context to produce structured summaries and conventional-commit titles directly from code changes.

How do I write conventional commit PR titles from code changes automatically?▼

You can generate conventional commit PR titles by processing branch context and diffs, which automatically enforces formatting rules and adheres to a strict 72-character title limit for your merge requests.

Does this PR generation skill require linked issues to draft a summary?▼

No, linked issues are not strictly required, but when provided, the skill includes them in the structured summary to enhance PR governance and traceability for code reviewers.

What is the best way to summarize code changes for pull request reviewers?▼

The best way to summarize code changes for reviewers is to auto-draft a structured PR description that includes a summary of changes, rationale, and testing steps derived from your git diff.

How do I format a merge request description with testing steps included?▼

You can format a merge request description by auto-generating a structured document that explicitly includes sections for a summary, changes, and testing steps based on your branch context.

Related Skills

Explore More Software Engineering Skills→
shredbxshredbx

research-git-patterns

Extract implementation patterns and story context from Git history.

Community
Intermediate
yunseo-kimyunseo-kim
1

create-pr

Create GitHub pull requests with Conventional Commits titles and structured bodies.

Community
Intermediate
kagentikagenti
292

repo:pr

Enforce standardized GitHub pull request titles and bodies with emoji and issue references.

Official
Basic
eveldeveld
10

write-pr-description

Generate structured pull request descriptions from diffs, commits, and issues.

Community
Intermediate