summarize-change

Analyzes branch changes and generates a structured change summary for pull request preparation.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill summarize-change-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summarize-change
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/summarize-change
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill summarize-change-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a consistent, well-structured pull request description from a branch full of commits is tedious and error-prone. This Skill automates the analysis of everything that changed since the branch diverged from the default branch and produces a standardized change summary with title, motivation, details, and a machine-readable change record. ## Core Features & Use Cases - Branch change analysis: Diffs the current branch against the default branch, consolidates commit entries, and resolves scope, type, and breaking-change flags. - Structured summary generation: Produces a newspaper-style summary with ## What, ## Why, and ## Details sections, plus a change-record YAML block consumed by downstream PR-creation skills. - Subagent drafting and auditing: Dispatches entry-drafter and lede-cutter subagents, then verifies, audits, and redispatches drafts with rejection codes when checks fail. - Use Case: After finishing a feature branch, invoke the Skill to produce a complete PR-ready change summary, including ticket references, work-type classification, and breaking-change markers, saved as a timestamped artifact. ## Quick Start Ask the agent to summarize the current branch's changes since it diverged from the default branch and generate the change summary for the pull request.

Frequently Asked Questions about summarize-change

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

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

Run the summarize-change Skill on your branch. It diffs against the default branch, consolidates commit entries, drafts change entries via a subagent, and renders What, Why, and Details sections plus a change-record block ready for PR creation.

How does the Skill determine the change type and scope?

It consolidates commit entries with the describe-change.mjs script, optionally fetches ticket labels via the GitHub CLI, and applies a work-type test to the diff. You can override scope and type with the --scope and --type flags, and a trailing exclamation mark marks the change as breaking.

Does summarize-change work with GitHub tickets and labels?

Yes. When the session context reports github as the SCM and a ticket ID exists, it fetches the issue's labels with gh issue view and resolves a ticket type from them. If the fetch fails, it continues without a ticket type and reports the failure.

What happens if the drafted change entries fail the audit?

The Skill redispatches the entry-drafter subagent with a rejection code such as unsupported-claim, subject, or voice, plus the failing passages. It allows at most two redispatches, after which it asks the developer to replace or explicitly accept the failing passages.

Where is the generated change summary saved?

The summary is saved as a timestamped Markdown artifact under the ticket directory derived from the session context, following the pattern timestamp_slug_change-summary.md. It includes a YAML frontmatter block with canonical and consumer fields read by downstream PR-creation skills.