summarize-changes
The summarize-changes command generates concise git-based summaries of development work across different timeframes and contexts. Use it to quickly create standup updates (today's work), weekly reports, pull request descriptions, or branch overviews by automatically gathering commit history, affected files, and changes relevant to your specified scope without manual log inspection.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/CloudAI-X/claude-workflow-v2/HEAD/commands/summarize-changes.md -o ~/.claude/commands/summarize-changes.mdsummarize-changes.md
## Context - Current branch: !`git branch --show-current` - Default branch: !`git remote show origin 2>/dev/null | grep 'HEAD branch' | cut -d' ' -f5 || echo "main"` - Today's commits: !`git log --oneline --since="midnight" --author="$(git config user.email)" 2>/dev/null || echo "No commits today"` - This week's commits: !`git log --oneline --since="1 week ago" --author="$(git config user.email)" 2>/dev/null | head -20 || echo "No commits this week"` - Branch commits (vs main): !`git log --oneline $(git remote show origin 2>/dev/null | grep 'HEAD branch' | cut -d' ' -f5 || echo "main")..HEAD 2>/dev/null | head -20 || echo "No branch commits"` - Files changed on branch: !`git diff --stat $(git merge-base HEAD origin/$(git remote show origin 2>/dev/null | grep 'HEAD branch' | cut -d' ' -f5 || echo "main"))..HEAD 2>/dev/null | tail -5 || echo "No changes"` ## 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 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
Expert code review specialist. Use PROACTIVELY after writing or modifying code, before commits, when asked to review changes, PR review, code quality check, lint, or standards audit. Focuses on quality, security, performance, and maintainability.
Expert debugging specialist for errors, test failures, crashes, segmentation faults, memory leaks, timeouts, race conditions, deadlocks, and unexpected behavior. Use PROACTIVELY when encountering any error, exception, or failing test. Performs systematic root cause analysis.
Technical documentation specialist. Use for creating README files, API documentation, architecture docs, inline comments, user guides, changelogs, migration guides, release notes, FAQs, and troubleshooting docs. MUST BE USED when documentation is needed or when code changes require doc updates.
Master coordinator for complex multi-step tasks. Use PROACTIVELY when a task involves 2+ modules, requires delegation to specialists, needs architectural planning, or involves GitHub PR workflows. MUST BE USED for open-ended requests like "improve", "enhance", "build", "scale", "refactor", "add feature", "system design", "architecture", "complex task", or when implementing features from GitHub issues.
Code refactoring specialist for improving code quality, reducing technical debt, eliminating code smells, reducing complexity, and applying design patterns. Use PROACTIVELY when code needs restructuring, simplification, tech debt reduction, or when applying DRY/SOLID principles.
Security specialist for vulnerability detection, secure coding review, and security hardening. Use PROACTIVELY when handling authentication, authorization, encryption, secrets, credentials, OAuth, JWT, CORS, headers, user input, API keys, or sensitive data. Checks for OWASP Top 10 and common vulnerabilities.
Testing strategy specialist for designing test suites, writing tests, and ensuring comprehensive coverage. Use PROACTIVELY when adding new features, fixing bugs, improving test coverage, creating test plans, mocking strategies, handling flaky tests, or writing integration/E2E tests.
Add tests for recently changed files or specified code