commit-analytics: Claude skill | implexaback to searchcommit-analytics
Analyzes git commit history for patterns, productivity metrics, and team insights via GitHub API
SKILL.md
---
name: commit-analytics
description: Analyzes git commit history for patterns, productivity metrics, and team insights via GitHub API
version: 1.0.0
author: DevTools Team
tags: [git, analytics, productivity, github]
---
# Commit Analytics
Provides deep insights into your git commit history using the GitHub API. Generates productivity reports, tracks coding patterns, and visualizes team contribution metrics.
## Features
- Commit frequency analysis
- Author attribution and workload distribution
- File change heatmaps
- Commit message quality scoring
- Branch activity tracking
## Setup
```bash
export GITHUB_TOKEN=ghp_your_token_here
```
## Usage
```bash
python scripts/analyze.py report owner/repo --token $GITHUB_TOKEN
python scripts/analyze.py author-stats owner/repo --token $GITHUB_TOKEN
```
related skills
semantically similar in the cross-vendor indexdon't have the plugin yet? install it then click "run inline in claude" again.
+clearly identifies the data source (github api) and primary use case (productivity metrics, team insights)+lists concrete features (frequency analysis, author attribution, heatmaps, message scoring, branch tracking) rather than abstract claimsweaknesses
- ~no intent statement, decision points, output contract, or outcome signals - reads as a feature list, not a skill procedure
- ~trigger phrases are generic command invocations (analyze.py report) with no contextual variety or natural-language entry points
- ~no acknowledgment of failure modes (rate limits, missing repos, auth failures, malformed commits, empty histories), no recovery strategies
- ~procedure is skeletal: two bash examples with no step-by-step logic, no input validation, no intermediate outputs, no success criteria
