github-analysis
Analyze GitHub commits, generate PR reviews, calculate contributor leaderboards, and assess code quality. Use when analyzing git commits, reviewing code, generating GitHub activity reports, or tracking developer contributions.
npx skills add majiayu000/claude-skill-registry --skill github-analysis-dglowacki-mega-agent-v2-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# GitHub Analysis Analyze GitHub activity, review code, and track contributions. ## Quick Start Analyze commits from JSON file: ```bash python scripts/analyze_commits.py commits.json ``` Generate leaderboard: ```bash python scripts/calculate_leaderboard.py commits.json --period week ``` ## Commit Analysis ### What to Extract From each commit, analyze: - **Author & timestamp** - **Commit message quality** - Clear (explains what and why) - Vague (just what, no why) - Cryptic (no context) - **Files changed** (count and types) - **Lines added/removed** - **Code quality indicators** - TODOs added - FIXMEs added - Console.log/debugging code - Commented code - Large file changes (>500 lines) ### Quality Scoring **Commit Message Quality:** - Excellent (8-10): Clear what + why, follows conventions - Good (5-7): Clear what, some context - Poor (1-4): Vague or no context - Bad (0): Single word, "wip", "test" **Code Quality Indicators:** ```bash # Check for debugging code grep -r "console.log\|debugger\|print(" changed_files/ # Check for TODOs grep -r "TODO\|FIXME" changed_files/ | wc -l # Check for commented code grep -r "^[[:space:]]*//.*=\|^[[:space:]]*/\*" changed_files/ ``` ## PR Review T
- Quick Start
- Commit Analysis
- What to Extract
- Quality Scoring
- PR Review Template
- Contributor Leaderboard
- Metrics
- Scoring Formula
- Leaderboard Format
- Code Quality Metrics
- Complexity Analysis
- Code Churn
- Test Coverage
- Data Processing
python scripts/analyze_commits.py commits.json
python scripts/calculate_leaderboard.py commits.json --period week
Check for debugging code
grep -r "console.log\|debugger\|print(" changed_files/
Check for TODOs
grep -r "TODO\|FIXME" changed_files/ | wc -l
Check for commented code
grep -r "^[[:space:]]*//.*=\|^[[:space:]]*/\*" changed_files/
Count function complexity (rough estimate)
Functions with >4 nested levels or >50 linesWhat does the github-analysis skill do?
Analyze GitHub commits, generate PR reviews, calculate contributor leaderboards, and assess code quality. Use when analyzing git commits, reviewing code, generating GitHub activity reports, or tracking developer contributions.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill github-analysis-dglowacki-mega-agent-v2-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
