skills.rest
sato-dev1234
sato-dev1234COMMUNITY
Explore all skills by this author →
GitHub

describe-pr

Analyze git changes and generate PR descriptions following project templates.

Updated Aug 23, 2026
Search Tags:#automation#git#code-review#pull-request#pr-description#template-based#project-templates
One-click install
npx skills add https://github.com/sato-dev1234/claude-code-sample --skill describe-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: describe-pr
Source: https://github.com/sato-dev1234/claude-code-sample/tree/main/skills/describe-pr
Command: npx skills add https://github.com/sato-dev1234/claude-code-sample --skill describe-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating thorough PR descriptions can be time-consuming and error-prone when summarizing code changes. This Skill analyzes git changes and aligns them with project PR templates to produce consistent, ready-to-submit PR descriptions.

Core Features & Use Cases

  • Analyzes diffs to extract problem statements, root causes, and proposed solutions.
  • Generates sections aligned with the project's PR template, including DoD-style verification items and regression notes.
  • Useful for multi-repo and multi-language projects where PR descriptions must follow a standard format.

Quick Start

Provide a complete PR description by analyzing the most recent git changes and applying the project PR template.

Frequently Asked Questions about describe-pr

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

FAQPage Schema
How do I automatically generate a pull request description from git commits?▼

You can generate a pull request description by analyzing git commits and diffs to extract problem statements, root causes, and proposed solutions into a structured format aligned with your project template.

Can I use a template-based PR description generator for multi-language repositories?▼

Yes, template-based PR description generation applies to software repositories across multiple languages, analyzing affected files and code changes to produce standardized PR descriptions regardless of the programming language.

What should a structured PR description include for thorough code review?▼

A structured PR description should include a problem statement, root cause analysis, solution approach, DoD-style verification items, and regression notes derived from the analyzed code changes.

How do I align code changes with a project's PR template automatically?▼

To align code changes with a PR template, the tool analyzes diffs and affected files, then maps the extracted information into the template's required sections for a ready-to-submit description.

Does automated PR description generation work without configuring dependencies?▼

Automated PR description generation works without external dependencies, directly reading current branch changes and applying the existing project PR template to produce the output.

Why does writing PR descriptions manually take so much time and cause errors?▼

Writing PR descriptions manually is time-consuming and error-prone because summarizing code changes requires reviewing every diff and commit, whereas automation extracts this information directly from git changes.

Related Skills

Explore More Software Engineering Skills→
StartaleGroupStartaleGroup
3

pr-summary

Generate a PR summary by comparing branch differences and writing to ./report/PR_SUMMARY.MD.

Official
Intermediate
flosrnflosrn

create-pr

Create and push pull requests with auto-generated titles and descriptions.

Community
Intermediate
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
wyattowalshwyattowalsh
4

git-workflow

Generate conventional commit messages and pull request descriptions for Git operations.

Community
Intermediate