pr-describe

Analyze Git branch changes to generate Conventional Commits PR titles and descriptions.

Updated Dec 22, 2025
One-click install
npx skills add https://github.com/senior-sigan/llm-skills --skill pr-describe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-describe
Source: https://github.com/senior-sigan/llm-skills/tree/main/skills/pr-describe
Command: npx skills add https://github.com/senior-sigan/llm-skills --skill pr-describe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a repository's branch changes to produce a concise PR title and description suitable for code review and merging.

Core Features & Use Cases

  • Generate a Conventional Commits compliant title from branch changes.
  • Produce a descriptive PR body detailing changes, rationale, and impacted areas.
  • Use in workflows to auto-fill PR metadata across multiple branches and repos.

Quick Start

Describe the current branch changes to auto-create a conventional-commits compliant PR title and description.

Frequently Asked Questions about pr-describe

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

FAQPage Schema
How do I auto-generate a pull request title and description from git branch changes?

To auto-generate a pull request, this skill analyzes your git branch changes, commit history, and diffs to produce a concise PR title and description suitable for code review and merging.

Can I generate conventional commits compliant PR titles from unmerged branch commits?

Yes, you can generate conventional commits compliant PR titles by applying the skill to branches with commits not yet merged, analyzing the diff to craft a compliant title and descriptive body.

What do I need to generate a PR body detailing changes and rationale across multiple branches?

To generate a PR body detailing changes and rationale, you need access to the branch point, commit history, and diffs, which the skill uses to describe impacted areas across common codebases.

Does the PR generation work with both feature and bugfix workflows?

Yes, the PR generation works across common codebases and both feature and bugfix workflows, requiring access to the branch point and commit history to craft the descriptive body.

What is the best way to auto-fill PR metadata across multiple repos?

The best way to auto-fill PR metadata across multiple repos is using this skill in your workflows to analyze branch changes and produce conventional commits compliant titles and descriptions.

When should I not use automated PR title generation from git diffs?

You should not use automated PR title generation when you lack access to the branch point, commit history, or diffs, as the skill requires these to analyze changes and craft a descriptive body.