analyze-git-style

Analyze local git commit messages and generate teaching-focused CLI reports.

8|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/ccomkhj/skills --skill analyze-git-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-git-style
Source: https://github.com/ccomkhj/skills/tree/main/analyze-git-style
Command: npx skills add https://github.com/ccomkhj/skills --skill analyze-git-style

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Commit messages often fail to communicate the change, making reviews slower and future debugging harder, especially when the history spans many repositories.

Core Features & Use Cases

  • Cross-repository commit discovery: Finds all local git repositories and analyzes commits across all branches.
  • Quality scoring with a multi-dimension rubric: Rates commits on Clarity, Length, Imperative mood, Specificity, and Body appropriateness, while excluding merge/auto-generated commits.
  • Teaching-focused reporting: Produces a CLI report with spotlights, rewrite examples, pattern clusters, and improvement opportunities for a selected time window (today or last 7 days).
  • Cleanup candidate detection: Flags likely WIP/fixup/squash/throwaway messages for squashing before merging.

Quick Start

Run analyze-git-style on your local machine for the last 7 days by invoking the skill with --week.

Frequently Asked Questions about analyze-git-style

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

FAQPage Schema
How do I analyze git commit message quality across multiple local repositories?

To analyze git commit message quality across multiple local repositories, you can use a tool that discovers all local repositories, extracts commit metadata, and scores messages against a rubric covering clarity, length, imperative mood, specificity, and body appropriateness.

How do I generate a report for recent git history to coach my team on commit conventions?

Generating a report for recent git history to coach teams involves applying a time filter like today or the last 7 days to extract commits, analyze patterns, and output a deterministic CLI report with actionable rewrite examples and improvement opportunities.

What is the best way to identify WIP, fixup, and squash commit messages before merging?

The best way to identify WIP, fixup, and squash commit messages before merging is to run a cleanup candidate detection process that flags likely throwaway messages, allowing you to squash them and clean up your repository history.

How does conventional commit scoring evaluate code review coaching opportunities?

Conventional commit scoring evaluates code review coaching opportunities by rating commit messages on a multi-dimensional rubric, excluding merge and auto-generated commits, and clustering pattern issues to produce targeted teaching reports.

Can I filter git repository analytics to only show commits from the last week?

Yes, you can filter git repository analytics to only show commits from the last week by applying time-filtered workflows, such as invoking the analysis tool with a weekly flag, which scopes the commit extraction and scoring to recent changes.

How do I find all local git repositories for commit history mining?

To find all local git repositories for commit history mining, you use a cross-repository discovery mechanism that automatically locates repositories on your machine and extracts commit metadata and bodies across all branches for analysis.