summarize-changes

Summarize scoped diffs and commit ranges into PR descriptions, release notes, or handoffs.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mtk177a/skills --skill summarize-changes-mtk177a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: summarize-changes
Source: https://github.com/mtk177a/skills/tree/main/skills/summarize-changes
Command: npx skills add https://github.com/mtk177a/skills --skill summarize-changes-mtk177a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing accurate change communication is hard: diffs show what changed but not why, test status is often assumed rather than verified, and public release notes can accidentally leak internal operational details. This Skill turns an explicitly scoped change set into one audience-appropriate artifact while preserving evidence status, risks, and unknowns. ## Core Features & Use Cases - Scoped change summarization: Works from a supplied diff, path set, commit range, PR range, or staged-only local changes, and states exactly what is included and excluded. - Evidence-state preservation: Distinguishes observed, reported, inferred, unknown, and conflicting claims so unverified tests or inferred intent are never presented as confirmed facts. - Four output profiles: Produces a PR description with reviewer context, public release notes, an operational release handoff, or a shareable summary, following repository templates when present. - Use Case: After staging a feature, ask for a PR description covering only the staged changes; the Skill excludes unrelated unstaged work, states that tests were not run, and redacts any suspected credentials found in the diff. ## Quick Start Ask the agent to write a PR description for the current staged changes, including impact, test status, and remaining risks.

Frequently Asked Questions about summarize-changes

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

FAQPage Schema
How do I write a PR description from a git diff?▼

Provide the diff, commit range, or staged scope and request a PR description. The Skill builds an evidence-grounded change inventory, adds reviewer context such as purpose, scope, and verification status, and follows the repository's PR template when one exists.

How do I generate release notes from a commit range?▼

Specify the exact range, such as release-base..HEAD, and ask for public release notes. The output covers user-observable changes, confirmed breaking changes, and migration steps while excluding internal rollout, monitoring, and rollback details.

What is the difference between public release notes and an operational release handoff?▼

Public release notes contain only user-observable changes and migration information. An operational handoff preserves deployment dependencies, reported or observed verification, monitoring and rollback details, remaining work, and unknowns for the operations audience.

Does it claim tests passed when test files were modified?▼

No. The presence or modification of a test is not treated as evidence it ran. Verification is recorded as observed result, reported but not observed, not run, or unavailable, and conflicting evidence is disclosed rather than merged.

Can it update the PR or publish the release directly?▼

No. The Skill is strictly read-only: invoking it does not authorize file edits, PR updates, release creation, or pushes. It returns the drafted artifact so a separately authorized workflow can publish it.

What happens if no diff or change set is available?▼

The Skill reports that summarization did not run and identifies the missing input, such as a diff, commit range, or repository. It never fabricates a summary without a retrievable change set.