skills.rest
Marshall-Hallenbeck
Marshall-HallenbeckCOMMUNITY
Explore all skills by this author →
𝕏@mjhallenbeckGitHub

summarize-changes

Parse git diffs and commit logs into categorized Markdown reports.

5|1|Updated Oct 18, 2019
Search Tags:#automation#git#documentation#pull-request#version-control#summarize
One-click install
npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill summarize-changes-marshall-hallenbeck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: summarize-changes
Source: https://github.com/Marshall-Hallenbeck/dot_files/tree/main/.claude/skills/summarize-changes
Command: npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill summarize-changes-marshall-hallenbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual effort required to draft release notes or PR descriptions by automatically parsing git diffs and commit logs into structured, readable summaries.

Core Features & Use Cases

  • Automated Categorization: Automatically groups changes into features, bug fixes, refactors, and documentation updates.
  • Flexible Scope: Supports summarizing uncommitted changes, specific branches, or custom commit ranges.
  • Use Case: Use this tool before opening a pull request to generate a professional summary of your work, ensuring all relevant changes are captured while excluding unrelated noise.

Quick Start

Invoke the summarize-changes skill by typing the command followed by the branch name or commit range you wish to analyze.

Frequently Asked Questions about summarize-changes

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

FAQPage Schema
How do I automatically generate pull request descriptions from git commit logs?▼

You can automatically generate pull request descriptions by parsing git diffs and commit logs into categorized Markdown reports. This process identifies features, bug fixes, and refactoring tasks to ensure all relevant changes are captured.

What is the best way to summarize uncommitted git changes for release notes?▼

To summarize uncommitted git changes for release notes, execute local git diff commands against your working directory. This parses updates into categorized Markdown reports, separating features and bug fixes for structured documentation.

Can I summarize changes for a specific branch or custom commit range?▼

Yes, you can summarize changes for a specific branch or custom commit range. By passing the branch name or commit range as an argument, the tool parses the targeted git history into a structured Markdown summary.

Do I need local git access to generate categorized Markdown reports from diffs?▼

Yes, local git access is required to generate these categorized Markdown reports. The summarization process directly executes diff and log commands against the current working directory to parse repository changes.

How does automated categorization handle refactoring tasks in version control summaries?▼

Automated categorization handles refactoring tasks by parsing git diffs and commit logs to isolate them from features and bug fixes. It groups structural code modifications into a distinct category within the generated Markdown report.

Related Skills

Explore More Software Engineering Skills→
faustellar1995faustellar1995
1

commit

Analyze staged git changes to draft commit messages.

Community
Intermediate
mgd34msumgd34msu
4

git-workflows

Generate pull request descriptions, commit messages, and release notes for Git workflows.

Community
Intermediate
julianobarbosajulianobarbosa
7

Diff

Automate Git workflow operations with GitHub CLI integration and security checks.

Community
Basic
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate