commit-analyzer 1.1.4 → 1.1.6

package/README.md

@@ -1,43 +1,29 @@
 # Git Commit Analyzer
 
-A TypeScript/Node.js program that analyzes git commits and generates categorized summaries using Claude CLI.
+A TypeScript/Node.js program that analyzes git commits and generates categorized
+summaries using Claude CLI.
 
 ## Features
 
 - Extract commit details (message, date, diff) from git repositories
-- Categorize commits using LLM analysis into: `tweak`, `feature`, or `process`
-- Generate CSV reports with year, category, summary, and description
-- Generate condensed markdown reports from CSV data for stakeholder communication
-- Support for multiple LLM models (Claude, Gemini, Codex) with automatic detection
+- Categorize commits using LLM analysis into:
+  `tweak`, `feature`, or `process`
+- Generate CSV reports with timestamp, category, summary, and description
+- Generate condensed markdown reports from CSV data for stakeholder
+  communication
+- Support for multiple LLM models (Claude, Gemini, OpenAI) with automatic
+  detection
 - Support for batch processing multiple commits
 - Automatically filters out merge commits for cleaner analysis
 - Robust error handling and validation
 
-## Prerequisites
-
-This tool requires Bun runtime. Install it globally:
-
-```bash
-# Install bun globally
-curl -fsSL https://bun.sh/install | bash
-# or
-npm install -g bun
-```
-
-## Installation
-
-```bash
-npm install
-bun link
-```
-
-After linking, you can use `commit-analyzer` command globally.
 
 ## Usage
 
 ### Default Behavior
 
-When run without arguments, the program analyzes all commits authored by the current user:
+When run without arguments, the program analyzes all commits authored by the
+current user:
 
 ```bash
 # Analyze all your commits in the current repository
@@ -56,9 +42,6 @@ npx commit-analyzer --author user@example.com
 # Analyze specific commits
 npx commit-analyzer abc123 def456 ghi789
 
-# Read commits from file
-npx commit-analyzer --file commits.txt
-
 # Specify output file with default behavior
 npx commit-analyzer --output analysis.csv --limit 20
 
@@ -69,32 +52,46 @@ npx commit-analyzer --report --input-csv analysis.csv
 npx commit-analyzer --report --limit 50
 
 # Use specific LLM model
-npx commit-analyzer --model claude --limit 10
+npx commit-analyzer --llm claude --limit 10
 ```
 
 ### Options
 
-- `-o, --output <file>`: Output file (default: `output.csv` for analysis, `summary-report.md` for reports)
-- `-f, --file <file>`: Read commit hashes from file (one per line)
-- `-a, --author <email>`: Filter commits by author email (defaults to current user)
-- `-l, --limit <number>`: Limit number of commits to analyze
-- `-m, --model <model>`: LLM model to use (claude, gemini, codex)
-- `-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
-- `-h, --help`: Display help
-- `-V, --version`: Display version
-
-### Input File Format
-
-When using `--file`, create a text file with one commit hash per line:
-
-```
-abc123def456
-def456ghi789
-ghi789jkl012
-```
+- `-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 version
 
 ## Output Formats
 
@@ -102,36 +99,46 @@ ghi789jkl012
 
 The program generates a CSV file with the following columns:
 
-- `year`: Year of the commit
-- `category`: One of `tweak`, `feature`, or `process`
-- `summary`: One-line description (max 80 characters)
-- `description`: Detailed explanation (2-3 sentences)
+- `timestamp`:
+  ISO 8601 timestamp of the commit (e.g., `2025-08-28T11:14:40.000Z`)
+- `category`:
+  One of `tweak`, `feature`, or `process`
+- `summary`:
+  One-line description (max 80 characters)
+- `description`:
+  Detailed explanation (2-3 sentences)
 
 ### Markdown Report Output
 
-When using the `--report` option, the program generates a condensed markdown report that:
+When using the `--report` option, the program generates a condensed markdown
+report that:
 
 - Groups commits by year (most recent first)
-- Organizes by categories: Features, Processes, Tweaks & Bug Fixes
+- Organizes by categories:
+  Features, Processes, Tweaks & Bug Fixes
 - Consolidates similar items for stakeholder readability
 - Includes commit count statistics
-- Uses professional language suitable for both technical and non-technical audiences
+- Uses professional language suitable for both technical and non-technical
+  audiences
 
 ## Requirements
 
-- Node.js 18+ with TypeScript support
+- Node.js 18+ with TypeScript support (Bun runtime recommended)
 - Git repository (must be run within a git repository)
 - At least one supported LLM CLI tool:
   - Claude CLI (`claude`) - recommended, defaults to Sonnet model
   - Gemini CLI (`gemini`)
-  - Codex CLI (`codex`)
+  - OpenAI CLI (`codex`)
 - Valid git commit hashes (when specifying commits manually)
 
 ## Categories
 
-- **tweak**: Minor adjustments, bug fixes, small improvements
-- **feature**: New functionality, major additions
-- **process**: Build system, CI/CD, tooling, configuration changes
+- **tweak**:
+  Minor adjustments, bug fixes, small improvements
+- **feature**:
+  New functionality, major additions
+- **process**:
+  Build system, CI/CD, tooling, configuration changes
 
 ## Error Handling
 
@@ -151,7 +158,8 @@ The tool automatically:
 - **Stops processing after a commit fails all retry attempts**
 - Exports partial results to the CSV file before exiting
 
-If the process stops (e.g., after 139 commits due to API failure), you can resume from where it left off:
+If the process stops (e.g., after 139 commits due to API failure), you can
+resume from where it left off:
 
 ```bash
 # Resume from last checkpoint
@@ -165,13 +173,12 @@ npx commit-analyzer --resume
 ```
 
 The checkpoint file (`.commit-analyzer/progress.json`) contains:
+
 - List of all commits to process
 - Successfully processed commits (including failed ones to skip on resume)
 - Analyzed commit data (only successful ones)
 - Output file location
 
-**Important**: When a commit fails after all retries (default 3), the process stops immediately to prevent wasting API calls. The successfully analyzed commits up to that point are saved to the CSV file.
-
 ### Application Data Directory
 
 The tool creates a `.commit-analyzer/` directory to store internal files:
@@ -185,23 +192,80 @@ The tool creates a `.commit-analyzer/` directory to store internal files:
     └── ...
 ```
 
-- **Progress checkpoint**: Enables resuming interrupted analysis sessions
-- **Analysis cache**: Stores LLM analysis results to avoid re-processing the same commits (TTL: 30 days)
+- **Progress checkpoint**:
+  Enables resuming interrupted analysis sessions
+- **Analysis cache**:
+  Stores LLM analysis results to avoid re-processing the same commits (TTL:
+  30 days)
 
 Use `--no-cache` to disable caching if needed.
+Use `--clear` to clear the cache and progress checkpoint.
+
+### Date Filtering
+
+The tool supports flexible date filtering using natural language or specific
+dates:
+
+```bash
+# 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:
+- Relative dates:
+  `"1 week ago"`, `"2 months ago"`, `"3 days ago"`
+- ISO dates:
+  `"2024-01-01"`, `"2024-12-31"`
+- Git-style dates:
+  Any format accepted by `git log --since` and `git log --until`
+
+### Batch Processing
+
+Control processing speed and resource usage with batch size options:
+
+```bash
+# 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
+```
 
 ### Retry Logic
 
-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.
+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.
 
 #### Configuration
 
 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)
+- `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)
 
 #### Examples
 
@@ -226,19 +290,19 @@ The retry mechanism automatically:
 
 ```bash
 # Install dependencies
-npm install
+bun install
 
 # Run in development mode
-npm run dev
+bun run dev
 
 # Build for production
-npm run build
+bun run build
 
 # Run linting
-npm run lint
+bun run lint
 
 # Type checking
-npm run typecheck
+bun run typecheck
 ```
 
 ## Examples
@@ -253,10 +317,6 @@ 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
 
-# Analyze specific commits
-git log --oneline -5 | cut -d' ' -f1 > recent_commits.txt
-npx commit-analyzer --file recent_commits.txt --output recent_analysis.csv
-
 # Quick analysis of your recent work
 npx commit-analyzer --limit 10
 
@@ -267,8 +327,30 @@ npx commit-analyzer --report --limit 100 --output yearly_analysis.csv
 npx commit-analyzer --report --input-csv existing_analysis.csv --output team_report.md
 
 # Use specific LLM model for analysis
-npx commit-analyzer --model gemini --limit 25
+npx commit-analyzer --llm gemini --limit 25
 
 # Resume interrupted analysis with progress tracking
 npx commit-analyzer --resume
 ```
+
+## Development
+
+This tool requires the Bun runtime.
+Install it globally:
+
+```bash
+# Install bun globally
+curl -fsSL https://bun.sh/install | bash
+# or
+npm install -g bun
+```
+
+## Installation
+
+```bash
+bun install
+bun build
+bun link
+```
+
+After linking, you can use `commit-analyzer` command globally.

package/package.json

@@ -1,6 +1,7 @@
 {
   "name": "commit-analyzer",
-  "version": "1.1.4",
+  "version": "1.1.6",
+  "files": ["dist"],
   "description": "Analyze git commits and generate categories, summaries, and descriptions for each commit. Optionally generate a yearly breakdown report of your commit history.",
   "main": "dist/main.ts",
   "bin": {

package/.claude/settings.local.json

@@ -1,23 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash(mkdir:*)",
-      "Bash(bun install:*)",
-      "Bash(bun run:*)",
-      "Bash(bun link:*)",
-      "Bash(npm run typecheck:*)",
-      "Bash(npm run lint)",
-      "Bash(npm run build:*)",
-      "Bash(npm run dev:*)",
-      "Bash(bun dev:*)",
-      "Bash(git log:*)",
-      "Bash(git checkout:*)",
-      "Bash(npx ts-node:*)",
-      "Bash(node:*)",
-      "Bash(npm start:*)",
-      "Bash(bun:*)"
-    ],
-    "deny": [],
-    "ask": []
-  }
-}

package/commits.csv

@@ -1,2 +0,0 @@
-year,category,summary,description
-2025,process,"Refactor project structure with numbered layers, path aliases, and automated","Major architectural reorganization moving from nested directories to numbered layer structure (1.domain, 2.application, 3.presentation, 4.infrastructure). Implements TypeScript path aliases (@domain, @app, @presentation, @infra) for cleaner imports and adds ESLint plugin for automatic import sorting and organization. All files renamed to kebab-case and imports updated throughout the codebase to use the new alias system. This improves code maintainability, reduces import path complexity, and establishes consistent file organization patterns."

package/csv-to-report-prompt.md

@@ -1,97 +0,0 @@
-# LLM Prompt Template: CSV to Markdown Report Generation
-
-This is the prompt template to be used by the LLM service to generate condensed
-markdown reports from CSV commit analysis data.
-
-## Prompt Template
-
-```
-Analyze the following CSV data containing git commit analysis results and generate a condensed markdown development summary report.
-
-CSV DATA:
-{csv_content}
-
-INSTRUCTIONS:
-1. Group the data by year (descending order, most recent first)
-2. Within each year, group by category: Features, Process Improvements, and Tweaks & Bug Fixes
-3. Consolidate similar items within each category to create readable summaries
-4. Focus on what was accomplished rather than individual commit details
-5. Use clear, professional language appropriate for stakeholders
-
-CATEGORY MAPPING:
-- "feature" → "Features" section
-- "process" → "Processes" section  
-- "tweak" → "Tweaks & Bug Fixes" section
-
-CONSOLIDATION GUIDELINES:
-- Group similar features together (e.g., "authentication system improvements")
-- Combine related bug fixes (e.g., "resolved 8 authentication issues")
-- Summarize process changes by theme (e.g., "CI/CD pipeline enhancements")
-- Use bullet points for individual items within categories
-- Aim for 3-7 bullet points per category per year
-- Include specific numbers when relevant (e.g., "15 bug fixes", "3 new features")
-
-OUTPUT FORMAT:
-Generate a markdown report with this exact structure:
-
-```markdown
-# Development Summary Report
-
-## Commit Analysis
-- **Total Commits**: [X] commits across [YEAR_RANGE]
-- **[MOST_RECENT_YEAR]**: [X] commits ([X] features, [X] process, [X] tweaks)
-- **[PREVIOUS_YEAR]**: [X] commits ([X] features, [X] process, [X] tweaks)
-- [Continue for each year in the data]
-
-## [YEAR]
-### Features
-- [Consolidated feature summary 1]
-- [Consolidated feature summary 2]
-- [Additional features as needed]
-
-### Processes
-- [Consolidated process improvement 1]
-- [Consolidated process improvement 2]
-- [Additional process items as needed]
-
-### Tweaks & Bug Fixes
-- [Consolidated tweak/fix summary 1]
-- [Consolidated tweak/fix summary 2]
-- [Additional tweaks/fixes as needed]
-
-## [PREVIOUS YEAR]
-[Repeat structure for each year in the data]
-```
-
-QUALITY REQUIREMENTS:
-- Keep summaries concise but informative
-- Use active voice and clear language
-- Avoid technical jargon where possible
-- Ensure each bullet point represents meaningful work
-- Make the report valuable for both technical and non-technical readers
-
-Generate the markdown report now:
-```
-
-## Implementation Notes
-
-This prompt should be used in the `MarkdownReportGenerator` service with the following approach:
-
-1. **Input Processing**: Replace `{csv_content}` with the actual CSV data read from the input file
-2. **LLM Call**: Send this prompt to the configured LLM (Claude, Gemini, etc.)
-3. **Response Parsing**: Extract the markdown content from the LLM response
-4. **File Output**: Write the generated markdown to the specified output file
-
-### Error Handling
-- If LLM returns malformed response, retry up to MAX_RETRIES times
-- Validate that the response contains properly formatted markdown
-- Ensure all years from the CSV data are represented in the output
-- Handle edge cases like empty categories or single-item categories
-
-### Response Validation
-The generated report should:
-- Start with "# Development Summary Report"
-- Have year sections in descending chronological order
-- Include all three category sections for each year (even if empty)
-- Use proper markdown formatting with ## for years and ### for categories
-- Contain bullet points (-) for individual items

package/eslint.config.mts

@@ -1,45 +0,0 @@
-import js from "@eslint/js"
-import { defineConfig } from "eslint/config"
-import simpleImportSort from "eslint-plugin-simple-import-sort"
-import globals from "globals"
-import tseslint from "typescript-eslint"
-
-export default defineConfig([
-  {
-    files: ["**/*.{js,mjs,cjs,ts,mts,cts}"],
-    plugins: { js },
-    extends: ["js/recommended"],
-    languageOptions: { globals: globals.node },
-  },
-  tseslint.configs.recommended,
-  {
-    plugins: {
-      "simple-import-sort": simpleImportSort,
-    },
-    rules: {
-      "simple-import-sort/imports": [
-        "warn",
-        {
-          groups: [
-            // Side effect imports
-            ["^\\u0000"],
-            // Packages. `react` related packages come first.
-            ["^react", "^@?\\w"],
-            // Aliases (adjust these regexes for your aliases)
-            ["^@domain"],
-            ["^@app"],
-            ["^@presentation"],
-            ["^@infra"],
-            // Parent imports
-            ["^\\.\\.(?!/?$)", "^\\.\\./?$"],
-            // Relative imports
-            ["^\\./(?=.*/)(?!/?$)", "^\\.(?!/?$)", "^\\./?$"],
-            // Style imports
-            ["^.+\\.s?css$"],
-          ],
-        },
-      ],
-      "simple-import-sort/exports": "warn",
-    },
-  },
-])

package/prompt.md

@@ -1,69 +0,0 @@
-# Prompt for Git Commit Analysis Program
-
-  Create a TypeScript/Node.js program that analyzes git commits and generates
-  categorized summaries.
-
-  The program should:
-
-## Input Requirements
-
-  - Accept a list of git commit hashes as input (command line arguments or file)
-  - For each commit, extract the commit message, date, and diff
-
-  Core Functionality:
-
-  1. Git Integration:
-     Use git show and git diff to get commit details and changes
-  2. LLM Analysis:
-     Send commit message + diff to the claude cli for categorization.
-  3. CSV Export:
-     Generate output with columns:
-     year, category, summary, description
-
-## LLM Prompt Template
-
-  Analyze this git commit and provide a categorization:
-
-  - COMMIT MESSAGE:
-    {commit_message}
-  - COMMIT DIFF:
-    {diff_content}
-
-  Based on the commit message and code changes, categorize this commit as one
-  of:
-  - "tweak":
-    Minor adjustments, bug fixes, small improvements
-  - "feature":
-    New functionality, major additions
-  - "process":
-    Build system, CI/CD, tooling, configuration changes
-
-  Provide:
-  1. Category:
-     [tweak|feature|process]
-  2. Summary:
-     One-line description (max 80 chars)
-  3. Description:
-     Detailed explanation (2-3 sentences)
-
-  Format as JSON: 
-  ```json
-  { 
-    "category": "...", 
-    "summary": "...",
-    "description": "..."
-  }
-  ```
-
-### Technical Implementation
-
-  - Use Node.js with TypeScript
-  - Extract year from git commit timestamp
-
-  Output Format:
-
-  CSV with headers:
-  year,category,summary,description
-
-  The program should be robust, handle edge cases, and provide clear error
-  messages for invalid commits or API failures.