git-commit-summarizer

Included with Lifetime

$97 forever

Summarizes git commits for specified users over a given time period and generates markdown reports

Writing & Docs

What this skill does


# Git Commit Summarizer

This skill analyzes git commit history for specified users and generates detailed markdown summary reports. It helps track developer contributions, code changes, and project progress over time.

## Capabilities

- **User-Specific Analysis**: Summarize commits for one or multiple git users
- **Time-Based Filtering**: Analyze commits from today or over specified number of days
- **Report Generation**: Create detailed markdown reports with commit statistics
- **File Organization**: Automatically save reports to `.claude/git_commit_report/` directory
- **Multi-User Support**: Process multiple users in a single execution

## Input Requirements

The skill requires:
- **Usernames**: One or more git usernames (comma-separated)
- **Days**: Optional number of days to analyze (defaults to today)

**Example Input Format**:
```
@git-commit-summarizer
Usernames: john.doe,jane.smith,alex.wong
Days: 7
```

## Output Formats

**Report Files**: Markdown files saved to `[current_repository]/.claude/git_commit_report/`
- Filename format: `[username]-[date].md`
- Each report includes:
  - User information and analysis period
  - Total commit count
  - Commit details (hash, date, message, files changed)
  - Statistics (commits per day, files per commit)
  - Summary of changes

**Console Output**: Summary of processing results and report locations

## How to Use

"Summarize git commits for user 'john.doe' over the last 3 days"
"Generate commit reports for 'alice,bob,charlie' for today"
"Analyze all commits by 'dev-team' in the last 14 days"

## Scripts

- `git_commit_analyzer.py`: Main module for analyzing git commits and generating reports
- `report_generator.py`: Creates formatted markdown reports from commit data

## Best Practices

1. **Repository Context**: Run this skill within a git repository directory
2. **User Names**: Use exact git usernames as they appear in commit history
3. **Time Range**: Specify days when you need historical analysis (default is today)
4. **Report Location**: Reports are saved in `.claude/git_commit_report/` for easy access
5. **Multiple Users**: Use comma-separated format for analyzing multiple users at once

## Limitations

- Requires git repository with commit history
- Only analyzes commits from the current repository
- Usernames must match exactly as in git commit history
- Time-based filtering uses relative days from current date
- Cannot analyze commits from remote repositories without local clone

Files: 8

Size: 42.2 KB

Complexity: 41/100

Category: Writing & Docs

Source: https://github.com/chaorenex1/coding-workflow/tree/main/skills/git-commit-summarizer

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts