commit-analyzer
Advanced tools
Analyze git commits and generate categories, summaries, and descriptions for each commit. Optionally generate a yearly breakdown report of your commit history.
A TypeScript/Node.js program that analyzes git commits and generates categorized summaries using Claude CLI.
tweak, feature, or processWhen run without arguments, the program analyzes all commits authored by the current user:
# Analyze all your commits in the current repository
npx commit-analyzer
# Analyze your last 10 commits
npx commit-analyzer --limit 10
# Analyze commits by a specific user
npx commit-analyzer --author user@example.com
# Analyze specific commits
npx commit-analyzer abc123 def456 ghi789
# Specify output file with default behavior
npx commit-analyzer --output analysis.csv --limit 20
# Generate markdown report from existing CSV
npx commit-analyzer --report --input-csv analysis.csv
# Analyze commits and generate both CSV and markdown report
npx commit-analyzer --report --limit 50
# Use specific LLM model
npx commit-analyzer --llm claude --limit 10
-o, --output <file>:
Output file (default:
results/commits.csv for analysis, results/report.md for reports)--output-dir <dir>:
Output directory for CSV and report files (default:
current directory)-a, --author <email>:
Filter commits by author email (defaults to current user)-l, --limit <number>:
Limit number of commits to analyze--llm <model>:
LLM model to use (claude, gemini, openai)-r, --resume:
Resume from last checkpoint if available-c, --clear:
Clear any existing progress checkpoint--report:
Generate condensed markdown report from existing CSV--input-csv <file>:
Input CSV file to read for report generation-v, --verbose:
Enable verbose logging (shows detailed error information)--since <date>:
Only analyze commits since this date (YYYY-MM-DD, '1 week ago', '2024-01-01')--until <date>:
Only analyze commits until this date (YYYY-MM-DD, '1 day ago', '2024-12-31')--no-cache:
Disable caching of analysis results--batch-size <number>:
Number of commits to process per batch (default:
1 for sequential processing)-h, --help:
Display help-V, --version:
Display versionThe program generates a CSV file with the following columns:
timestamp:
ISO 8601 timestamp of the commit (e.g., 2025-08-28T11:14:40.000Z)category:
One of tweak, feature, or processsummary:
One-line description (max 80 characters)description:
Detailed explanation (2-3 sentences)When using the --report option, the program generates a condensed markdown
report that:
claude) - recommended, defaults to Sonnet modelgemini)codex)The program includes comprehensive error handling for:
The tool automatically:
If the process stops (e.g., after 139 commits due to API failure), you can resume from where it left off:
# Resume from last checkpoint
npx commit-analyzer --resume
# Clear checkpoint and start fresh
npx commit-analyzer --clear
# View checkpoint status (it will prompt you)
npx commit-analyzer --resume
The checkpoint file (.commit-analyzer/progress.json) contains:
The tool creates a .commit-analyzer/ directory to store internal files:
.commit-analyzer/
├── progress.json # Progress checkpoint data
└── cache/ # Cached analysis results
├── commit-abc123.json
├── commit-def456.json
└── ...
Use --no-cache to disable caching if needed.
Use --clear to clear the cache and progress checkpoint.
The tool supports flexible date filtering using natural language or specific dates:
# Analyze commits from the last week
npx commit-analyzer --since "1 week ago"
# Analyze commits from a specific date range
npx commit-analyzer --since "2024-01-01" --until "2024-12-31"
# Analyze commits from the beginning of the year
npx commit-analyzer --since "2024-01-01"
# Analyze commits up to a specific date
npx commit-analyzer --until "2024-06-30"
Date formats supported:
"1 week ago", "2 months ago", "3 days ago""2024-01-01", "2024-12-31"git log --since and git log --untilControl processing speed and resource usage with batch size options:
# Process commits one at a time (default, safest for rate limits)
npx commit-analyzer --batch-size 1
# Process multiple commits in parallel (faster but may hit rate limits)
npx commit-analyzer --batch-size 5 --limit 100
# Sequential processing for large datasets
npx commit-analyzer --batch-size 1 --limit 500
The tool includes automatic retry logic with exponential backoff for handling API failures when processing many commits. This is especially useful when analyzing large numbers of commits that might trigger rate limits.
You can configure the retry behavior using environment variables:
LLM_MAX_RETRIES:
Maximum number of retry attempts (default:
3)LLM_INITIAL_RETRY_DELAY:
Initial delay between retries in milliseconds (default:
5000)LLM_MAX_RETRY_DELAY:
Maximum delay between retries in milliseconds (default:
30000)LLM_RETRY_MULTIPLIER:
Multiplier for exponential backoff (default:
2)# More aggressive retries for large batches (e.g., 139+ commits)
LLM_MAX_RETRIES=5 LLM_INITIAL_RETRY_DELAY=10000 npx commit-analyzer --limit 200
# Faster retries for testing
LLM_MAX_RETRIES=2 LLM_INITIAL_RETRY_DELAY=2000 npx commit-analyzer
# Conservative approach for rate-limited APIs
LLM_MAX_RETRIES=4 LLM_INITIAL_RETRY_DELAY=15000 LLM_MAX_RETRY_DELAY=60000 npx commit-analyzer
The retry mechanism automatically:
# Install dependencies
bun install
# Run in development mode
bun run dev
# Build for production
bun run build
# Run linting
bun run lint
# Type checking
bun run typecheck
# Analyze all your commits in the current repository
npx commit-analyzer
# Analyze your last 20 commits and save to custom file
npx commit-analyzer --limit 20 --output my_analysis.csv
# Analyze commits by a specific team member
npx commit-analyzer --author teammate@company.com --limit 50
# Quick analysis of your recent work
npx commit-analyzer --limit 10
# Generate both CSV and markdown report from analysis
npx commit-analyzer --report --limit 100 --output yearly_analysis.csv
# Generate only a markdown report from existing CSV
npx commit-analyzer --report --input-csv existing_analysis.csv --output team_report.md
# Use specific LLM model for analysis
npx commit-analyzer --llm gemini --limit 25
# Resume interrupted analysis with progress tracking
npx commit-analyzer --resume
This tool requires the Bun runtime. Install it globally:
# Install bun globally
curl -fsSL https://bun.sh/install | bash
# or
npm install -g bun
bun install
bun build
bun link
After linking, you can use commit-analyzer command globally.
FAQs
Analyze git commits and generate categories, summaries, and descriptions for each commit. Optionally generate a yearly breakdown report of your commit history.
The npm package commit-analyzer receives a total of 547 weekly downloads. As such, commit-analyzer popularity was classified as not popular.
We found that commit-analyzer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
OpenSSF has issued a high-severity advisory warning open source developers of an active Slack-based campaign using impersonation to deliver malware.
Research
/Security News
Malicious packages published to npm, PyPI, Go Modules, crates.io, and Packagist impersonate developer tooling to fetch staged malware, steal credentials and wallets, and enable remote access.
Security News
Microsoft has released an open source toolkit for enforcing runtime security policies on AI agents as adoption accelerates faster than governance controls.