summarize-recent-changes

Summarize recent git commits and uncommitted working-tree changes into concise reports.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill summarize-recent-changes-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summarize-recent-changes
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/summarize-recent-changes
Command: npx skills add https://github.com/catalystctl/catcode --skill summarize-recent-changes-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When returning to a repository or finishing a work session, it is hard to quickly recall what changed recently. This Skill inspects the git history and working tree to produce a concise, well-organized summary of the latest commits and any uncommitted edits. ## Core Features & Use Cases - Working tree inspection: Uses git_status to determine whether recent changes are committed, uncommitted, or both. - Commit analysis: Reads recent git_log entries and drills into the HEAD commit with git show --stat and the full commit message to capture scope and rationale. - Diff review: Examines staged and unstaged diffs via git_diff when the working tree is dirty. - Use Case: After a long coding session, ask "what did you just do" and receive a grouped summary of the HEAD commit and any pending edits, preserving the author's severity labels and component structure. ## Quick Start Ask the agent to summarize the most recent changes in this repository, including the latest commit and any uncommitted edits.

Frequently Asked Questions about summarize-recent-changes

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

FAQPage Schema
How do I summarize recent git changes in a repository?

Run git_status to check the working tree, then use git_log for recent commits and git_diff for uncommitted edits. This Skill automates that sequence and groups the findings by component into a concise summary.

How to see what changed in the latest git commit?

Use git show --stat on the HEAD commit to see which files were touched, then read the full commit message with git log -1 --format to understand the author's rationale and grouping of changes.

Does this Skill work when the working tree is clean?

Yes. When the tree is clean, the most recent changes are defined as the HEAD commit, and the Skill reports that directly instead of fabricating broader scope from uncommitted edits.

Can summarizing recent changes modify my code?

No. The workflow is strictly read-only reconnaissance using git inspection commands. It never edits project files, stages changes, or creates commits while producing the summary.

What is the difference between summarizing changes and a codebase overview?

Summarizing recent changes reports on recent deltas such as the latest commits and uncommitted diffs. A codebase overview answers what the repository is as a whole, which is a separate skill for unfamiliar projects.