git-code-review

Analyze git commits by specified users over a defined time window and generate per-user markdown reports with file-level summaries and line-by-line feedback.

3|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/chaorenex1/coding-agent-workflow --skill git-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-code-review
Source: https://github.com/chaorenex1/coding-agent-workflow/tree/main/skills/git-code-review
Command: npx skills add https://github.com/chaorenex1/coding-agent-workflow --skill git-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes git commit history for specified users and generates comprehensive, structured code review reports, helping teams improve code quality with minimal manual effort.

Core Features & Use Cases

  • User-Specific Git History: Fetch commit history for one or multiple users.
  • Time-Based Filtering: Filter commits by days (defaults to current day).
  • Commit Analysis: Analyze changes, additions, and deletions.
  • Report Generation: Create markdown reports with recommendations and checks.
  • Automated Reporting: Save reports to organized directory structure.

Quick Start

Run the tool specifying users and time window to generate per-user review reports.

Frequently Asked Questions about git-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review from git commit history?

Automated code review analyzes git commits for specified users over a time window and generates markdown reports with file-level summaries and line-by-line feedback. This Skill fetches commit history, filters by user and days, and saves organized reports to .claude/git_code_review with per-user recommendations and quality checks.

Can I review commits from multiple users at once?

Yes, this Skill supports multi-user filtering. Specify multiple users to analyze their commits within a defined time period, and it generates separate markdown reports for each user with their changes, additions, deletions, and feedback organized by file.

What do I need to run git commit analysis?

You need a valid git repository, Git CLI available on your system, and read access to commit history. The Skill filters commits by specified users and optional days parameter, then outputs structured reports named username-date.md with a processing summary.

How are code review reports organized and where are they saved?

Reports are saved as markdown files in the current-repo/.claude/git_code_review directory with a username-date.md naming convention. Each report contains file-level summaries, line-by-line feedback, and recommendations organized by commit and changed files.

Can I filter commits by a specific time window?

Yes, the Skill accepts an optional days parameter to filter commits. It defaults to the current day but can be adjusted to analyze commits over a longer period, allowing you to scope reviews to specific time windows.

What information does the commit analysis include?

Analysis covers changes, additions, and deletions per commit, with per-file summaries and line-by-line feedback. Reports include quality checks and recommendations to help teams improve code quality, organized by user and time period.