pr-summary

Generates a structured pull-request summary from git diff, file list, commit history.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/eglenn-dev/dt-skills --skill pr-summary-eglenn-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-summary
Source: https://github.com/eglenn-dev/dt-skills/tree/main/skills/pr-summary
Command: npx skills add https://github.com/eglenn-dev/dt-skills --skill pr-summary-eglenn-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of pull request summaries, saving developers time and ensuring consistent, informative descriptions for code reviews.

Core Features & Use Cases

  • Automated Summary Generation: Creates a structured PR description based on git diffs, changed files, and commit logs.
  • Key Information Extraction: Identifies title, summary points, key changes by area, testing notes, and risk assessment.
  • Use Case: After pushing your feature branch, run this skill to get a draft PR description that you can then refine and submit.

Quick Start

Use the pr-summary skill to generate a pull request summary for your current branch changes.

Frequently Asked Questions about pr-summary

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

FAQPage Schema
How do I generate a pull request summary from branch changes?

To generate a pull request summary from branch changes, this skill analyzes your git diff, file list, and commit history to output a structured PR title, summary points, and categorized file changes.

What is the best way to automate code review descriptions for git branches?

Automating code review descriptions involves extracting key information from git diffs and commit logs. This skill creates a comprehensive overview of modifications, including testing suggestions and risk assessment, to facilitate efficient reviews.

Does this automated PR summary tool include risk assessment and testing suggestions?

Yes, the automated PR summary includes both risk assessment and testing suggestions. It evaluates the git diff and commit history to provide a comprehensive overview of modifications and potential impacts.

How to extract categorized file changes and commit history for a PR description?

Extracting categorized file changes and commit history for a PR description is done by analyzing the current branch changes. The skill processes the git diff to identify key changes by area and produces structured summary points.

Can I use this to draft a PR title and summary points from a feature branch?

Yes, you can use this to draft a PR title and summary points from a feature branch. After pushing your branch, run the skill to get a draft description based on the git diff and commit logs that you can refine and submit.

What git information is needed to create a structured pull request summary?

Creating a structured pull request summary requires your current branch's git diff, file list, and commit history. This data is analyzed to produce the PR title, categorized changes, and risk assessment.