Git Stats

What This Skill Does

The Git Stats skill for OpenClaw is a powerful analytical engine designed to provide deep insights into the health, productivity, and activity patterns of any local Git repository. By executing optimized Git commands locally, the agent parses commit history to extract meaningful metrics without ever leaving your machine. It generates professional-grade reports that highlight contributor performance, frequency of code changes, and potential technical debt hotspots within the file structure.

Installation

To integrate this capability into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/sa9saq/git-stats

Use Cases

• Project Auditing: Quickly assess the bus factor by identifying which contributors are responsible for the majority of the codebase.
• Bottleneck Identification: Pinpoint "hotspot" files that undergo the most changes, allowing teams to focus refactoring efforts on high-risk areas.
• Velocity Tracking: Visualize development trends over time to understand project maturity and sprint performance.
• Onboarding/Handovers: Provide new team members with an instant overview of the repository's history and active development patterns.

Example Prompts

1. "Generate a contributor ranking report for this repository from the last 6 months to see who is the most active."
2. "Show me the top 10 most changed files in the codebase so I can identify potential areas for refactoring."
3. "Analyze our development patterns; what time of day and which days of the week are we most productive?"

Tips & Limitations

• Deduplication: If you notice that the same author appears multiple times under different email addresses, create a .mailmap file in the root of your repo to standardize identities.
• Performance: On massive repositories with over 100,000 commits, the agent will automatically apply a one-year time filter to maintain performance. If you need a full history, be prepared for longer processing times.
• Accuracy: The skill is entirely local. It does not require API keys or external network connections, ensuring your proprietary code metadata remains private. Always run the skill from the root directory of your git project to ensure the git rev-parse verification succeeds.