Skip to main content
command CX Codex

summarize-changes — Claude Code command: summary, install

summarize-changes reads Git history and changed files to prepare standup notes, reports, or a PR description. Use it when a recent change summary needs a clear structure.

MIT ★ 1,424 updated 2026-10-06

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/summarize-changes.md
Open on GitHub

What summarize-changes does

The command queries Git through Bash(git:*). It reads the current and default branches, the Git user email, recent commits, branch history, and a diff stat. The result is arranged under Summary, Changes, Files, and Impact.

Pass today for a standup note, week for a weekly report, branch for the current branch, or pr for a full PR description. With no argument, the scope is today. The today and week modes filter the log again by the Git user email, so their summaries cover that user’s commits rather than everyone’s.

Branch work is compared with origin/HEAD; if the initial branch lists are empty, the command calculates the comparison against the default branch. Git must be available in the project, and the Git user email is used for the personal commit filter.

What it helps with

  • summarize today’s commits for standup
  • turn a week of Git history into a report
  • describe the current branch for a PR
  • list the main files changed
  • explain what the branch changes enable

Example prompts for the agent

  • Run /summarize-changes today and write my standup summary.
  • Use /summarize-changes week to prepare a report from my commits.
  • Create a full PR description with /summarize-changes pr.

How to install summarize-changes

Manually: put the files in place

.claude/commands/summarize-changes.md

Call it with /summarize-changes. For all projects use ~/.claude/commands/

Questions about summarize-changes

How do I install summarize-changes in Claude Code?

Save the command file as .claude/commands/summarize-changes.md.

What does summarize-changes do?

It inspects Git commits, branch history, and changed-file statistics, then formats the findings for a standup, report, documentation, or PR.

Which scopes does summarize-changes support?

It supports today, week, branch, and pr. The first two scopes keep only commits by the Git user, while an omitted argument uses today.

Source text

summarize-changes.md · MIT
---
allowed-tools: Bash(git:*)
description: Summarize recent changes for standup, PR, or documentation
argument-hint: "[today|week|branch|pr] (default: today)"
---

## Context

- Current branch: !`git branch --show-current`
- Default branch: !`git remote show origin 2>/dev/null | grep 'HEAD branch' | cut -d' ' -f5 || echo "main"`
- Git user: !`git config user.email 2>/dev/null || echo "unknown"`
- Today's commits (all authors): !`git log --oneline --since="midnight" 2>/dev/null || echo "No commits today"`
- This week's commits (all authors): !`git log --oneline --since="1 week ago" 2>/dev/null | head -20`
- Branch commits (vs origin's default branch): !`git log --oneline origin/HEAD..HEAD 2>/dev/null | head -20`
- Files changed on branch: !`git diff --stat origin/HEAD...HEAD 2>/dev/null | tail -5`

## Task

Generate a clear, concise summary based on the scope:

1. **today**: What I did today (for standup)
2. **week**: Weekly summary (for reports)
3. **branch**: All changes on this branch (for PR)
4. **pr**: Full PR description with sections

For **today** and **week**, report only the git user's own commits: re-run the log with `--author=<git user>` using the address shown above. If the two branch lists above are empty, compute them against the default branch shown above.

Format the output as:
- **Summary**: 1-2 sentence overview
- **Changes**: Bullet list of key changes
- **Files**: Main files affected
- **Impact**: What this enables or fixes

Scope: $ARGUMENTS

© CloudAI-X · MIT · CloudAI-X/claude-workflow-v2

Similar slash commands

All slash commands for Git and GitHub →

From the same set46

The whole set →

Project sponsors

Companies that keep this analytics open