Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Analyzes a git repository's commit history and produces reports covering contributor rankings, file change frequency, and commit message quality scores. Configurable time windows, branch filters, and output formats (markdown, JSON, plain text) are supported. Designed for team leads and developers who want visibility into how a codebase evolves.
Combines frequency, contributor, heatmap, and message quality analysis into a single command instead of requiring multiple git log invocations and manual aggregation.
When to use it
- Reviewing contributor activity before a quarterly engineering retrospective
- Identifying the most frequently modified files to prioritize refactoring work
- Auditing commit message quality before enforcing conventional commits on a team
- Generating a JSON commit report as a CI quality gate in a pull request workflow
- Filtering one developer's commits over a custom date range for a code review
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Show me commit quality for the last 90 days on the develop branch
- 1Runs the analyzer against the develop branch with a 90-day window
- 2Walks commit history and scores each message against five quality criteria
- 3Aggregates per-criterion pass rates into an overall percentage score
- 4Identifies and lists the worst-offending commit messages by pattern
- 5Outputs a formatted markdown report to stdout
A markdown report showing an overall quality score out of 100, per-criterion pass rates, and the specific vague or malformed commit messages that lowered the score