Skip to content
cccskills
FreePublished on GitHub

summarize-changes-headless

Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Current changes

!git diff HEAD

Instructions

If the diff above is empty, output exactly: No uncommitted changes.

Otherwise, output the summary in the following format with no surrounding prose:

SUMMARY
- [bullet point describing the first logical change]
- [bullet point describing the second logical change]
[continue as needed, two to five bullets maximum]

RISKS
- [risk] or NONE

Rules for the SUMMARY section:

  • Each bullet describes a logical change, not a file change. If three files were modified to implement one feature, that is one bullet.
  • Use present tense: "Add validation for email field" not "Added" or "Adding".
  • Maximum 80 characters per bullet.

Rules for the RISKS section:

  • List only genuine risks: missing error handling, hardcoded credentials, removed tests, breaking API changes.
  • If there are no risks, write NONE on a single line.
  • Do not list stylistic observations as risks.

Output nothing else. No preamble, no "Here is the summary:", no closing remarks. The output must be parseable by a script that splits on the SUMMARY and RISKS headers.


Note: this skill is optimized for headless use with claude -p "/summarize-changes-headless". The concise, structured output can be captured with claude -p "/summarize-changes-headless" > summary.txt and processed by downstream tools. Compare this to the interactive summarize-changes skill, which produces more readable prose suited to an interactive session. In headless mode, conciseness and consistent structure matter more than readability, because there is no follow-up turn to ask for clarification or a reformatted response.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.

The English summary is being prepared. Showing the original description.

davila7/claude-with-skills13Updated May 15, 2026

REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.

The English summary is being prepared. Showing the original description.

davila7/claude-with-skills13Updated May 15, 2026

Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.

The English summary is being prepared. Showing the original description.

davila7/claude-with-skills13Updated May 15, 2026

Create a git branch named after a GitHub issue.

The English summary is being prepared. Showing the original description.

davila7/claude-with-skills13Updated May 15, 2026

Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.

The English summary is being prepared. Showing the original description.

davila7/claude-with-skills13Updated May 15, 2026

Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.

The English summary is being prepared. Showing the original description.

davila7/claude-with-skills13Updated May 15, 2026

See all skills by davila7

Report a problem with this skill