custom-pr-summary

Generate a GitHub pull request summary from feature documentation for the current branch.

2|1|Updated Feb 19, 2026

Search Tags:#developer tools #code review #documentation #github #pr #summary

Ready to run

npx skills add https://github.com/assertchris/claude-skills --skill custom-pr-summary

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: custom-pr-summary
Source: https://github.com/assertchris/claude-skills/tree/main/custom-pr-summary
Command: npx skills add https://github.com/assertchris/claude-skills --skill custom-pr-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the pull request process by automatically generating concise summaries from feature documentation, saving developers time and improving code review efficiency.

Core Features & Use Cases

Automated Summary Generation: Creates a brief overview, lists changed files, and highlights key review areas from feature docs.
Streamlined Code Reviews: Provides reviewers with essential information upfront, reducing the need to sift through lengthy documents.
Use Case: After completing a feature, run this skill to get a ready-to-paste PR description that clearly communicates the changes and their impact.

Quick Start

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

Frequently Asked Questions about custom-pr-summary

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

FAQPage Schema

How do I generate a concise PR summary for my current branch?▼

To generate a concise PR summary, the Skill reads your feature documentation from the 'features/' directory and uses git commands to detect the current branch. It outputs a brief overview, lists changed files grouped by type, and highlights key files for reviewer focus.

What is the best way to automatically list changed files in a GitHub pull request?▼

To automatically list changed files in a GitHub pull request, this Skill parses your feature documentation and groups changed files by type. It extracts this information by analyzing the branch's feature docs to provide a ready-to-paste PR description.

Can I generate a PR description from feature docs without manually writing code changes?▼

Yes, you can generate a PR description directly from feature docs without manually writing summaries. The Skill locates feature documents in the 'features/' directory to automatically extract overviews and identify key review areas.

Does generating a pull request summary require specific git commands or branch setup?▼

Generating a pull request summary requires git commands to detect the current branch and locate feature documents in the 'features/' directory. Your repository must contain these feature documents for the Skill to extract the necessary overview and changed file lists.

Why use feature documentation to create code review summaries instead of diff analysis?▼

Using feature documentation to create code review summaries provides essential context upfront, reducing the need for reviewers to sift through lengthy documents. It extracts an overview and highlights key files for reviewer focus directly from the feature specs.

Are there limitations when extracting a PR overview from the features directory?▼

A limitation when extracting a PR overview is that the Skill requires feature documents to be present in the 'features/' directory. Without these documents, it cannot detect the branch context or generate the grouped changed files list for your pull request.