summarize-changes

summarize-changes is a skill for Claude Code from davila7/claude-with-skills. It costs 42 tokens per session (262 once invoked), scanned A, original, MIT.

A summary of uncommitted changes in a Git project, where Git records versions of files and their history. It describes the intended changes and flags risks before a commit.

In plain words
What is it for?
Use it to understand the current diff, prepare a commit message, or check changes before committing.
Why use it?
It gives a quick review of pending work and can reveal issues such as missing error handling, exposed configuration, removed tests, or mixed refactors.

Skill for Claude Code

Written for Claude Code: dynamic context !`command`. Also seen: mentions Claude Code.

Good fit Use it to understand the current diff, prepare a commit message, or check changes before committing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davila7/claude-with-skills/summarize-changes
About the project

Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.

davila7/claude-with-skills · 11 stars · on GitHub · claude-with-skills.vercel.app

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add davila7/claude-with-skills --skill summarize-changes
Clone the repo
git clone --depth 1 https://github.com/davila7/claude-with-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for summarize-changes

README.md
[![agentmods](https://agentmods.dev/badge/skills/davila7/claude-with-skills/summarize-changes/github.svg)](https://agentmods.dev/skills/davila7/claude-with-skills/summarize-changes)
Your own site
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/summarize-changes"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/summarize-changes/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for summarize-changes

Your own site · 80×15
<a href="https://agentmods.dev/skills/davila7/claude-with-skills/summarize-changes"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/summarize-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.00262
Opus 5 $0.00021 $0.00131
Sonnet 5 $0.00008 $0.00052
Haiku 4.5 $0.00004 $0.00026

Measured 9d ago against content hash 66ae44f37dd2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

summarize-changes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

src/content/docs/01-basic/lesson-05-invoking/examples/summarize-changes/SKILL.md · 28 lines

What it actually says

Current changes

!git diff HEAD

Instructions

Summarize the changes above in two or three bullet points. Focus on the logical intent of the changes, not the line-by-line diff.

Then list any risks you observe, such as:

  • Missing error handling on new code paths
  • Hardcoded values (API URLs, credentials, magic numbers) that should be configuration
  • Removed tests or disabled assertions
  • Changes to public API signatures or exported interfaces
  • Large refactors mixed with behavior changes (should be separate commits)

If the diff is empty, say there are no uncommitted changes.


Note for learners: the ! backtick line above is dynamic context injection. When Claude Code activates this skill, it runs git diff HEAD and replaces that line with the real diff output before Claude reads the file. The result is that Claude sees the actual diff as part of the skill body, without needing a separate tool call. This is the canonical example from the Claude Code skills documentation.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 28 lines · 42 tokens per session scan A 66ae44f37dd2

Subscribe to this mod's changes

summarize-changes is a skill published in the GitHub repository davila7/claude-with-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 262 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens