change-summary

Generate imperative PR titles and structured change summaries for code reviews.

Updated Feb 23, 2026

Search Tags:#documentation #merge-request #pr-description #summary-generation #change-summary #feature-summary

Ready to run

npx skills add https://github.com/schirrmacher/coding --skill change-summary-schirrmacher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-summary
Source: https://github.com/schirrmacher/coding/tree/main/skills/change-summary
Command: npx skills add https://github.com/schirrmacher/coding --skill change-summary-schirrmacher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a clear, user-facing summary of code changes to accompany pull requests, saving reviewers time and avoiding ambiguous messaging.

Core Features & Use Cases

Generate a concise, imperative PR title (max 60 chars) and a structured description that highlights the changes.
List user-facing changes by feature or API change in plain language for reviewers.
Provide ready-to-copy PR narrative and examples tailored for code reviews.

Quick Start

Provide a concise PR summary for the current branch.

Frequently Asked Questions about change-summary

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

FAQPage Schema

How do I generate a PR summary for a feature branch?▼

You can generate a PR summary for a feature branch by analyzing code changes to produce a structured PR description. This yields an imperative title under 60 characters and a 3-5 bullet list highlighting behavior changes for reviewers.

What is the best way to write a merge request description from code changes?▼

The best way to write a merge request description from code changes is to summarize the diffs into plain language. This produces ready-to-paste narrative snippets that highlight API or behavior changes, saving reviewers time.

Can I automatically list API changes for code reviewers?▼

Yes, you can automatically list API changes for code reviewers by summarizing feature branch modifications. The output provides a structured What changed section that details user-facing feature and API updates in plain language.

Does PR summary generation work without adding dependencies?▼

Yes, PR summary generation can work without adding dependencies. You can summarize code changes into a clear PR description without requiring external components, directly producing an imperative title and ready-to-paste snippets.

Why use automated summary generation instead of manually writing PR descriptions?▼

Automated summary generation avoids ambiguous messaging and saves reviewers time by extracting plain language summaries from code changes. It consistently produces an imperative title and structured feature summaries, unlike manual writing which can miss key API changes.