tools-repo-review
Comprehensive GitHub repository analysis for engineering managers with contribution stats, code quality review, team health metrics, and actionable management outputs
npx skills add majiayu000/claude-skill-registry --skill tools-repo-review --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.
# Repo Review Skill (Engineering Manager Edition) This skill enables AI-powered repository analysis with three modes: contribution statistics, code quality assessment, and team/manager insights. Supports org-wide reviews, single repos, and saved repo groups. ## Prerequisites - Git CLI installed - GitHub CLI (`gh`) for org-wide reviews - Optional: Python 3.10+ with matplotlib for PNG chart generation ## Quick Start ``` Review https://github.com/org/repo Review the UP organization Review my side-projects group ``` ## Progressive Onboarding On first use, gather context through conversation: ### Initial Questions 1. **Role**: Engineering Manager | Tech Lead | IC 2. **Focus**: Full review | Quick stats | Code quality only 3. **Time period**: 30 days | 90 days | YTD | Custom Save preferences to `config.yaml` for future sessions. ### Follow-up Questions (as needed) - "I found 5 contributors. Focus on anyone specific?" - "Compare against previous review?" - "Flag contributors with < X commits?" --- ## Analysis Modes ### Mode 1: Contribution Statistics Gather quantitative metrics using git commands: ```bash # Clone repo to temp directory git clone --quiet <repo_url> /tmp/repo_review_temp #
- Prerequisites
- Quick Start
- Progressive Onboarding
- Initial Questions
- Follow-up Questions (as needed)
- Analysis Modes
- Mode 1: Contribution Statistics
- Mode 2: Code Quality Review
- Mode 3: Team/Manager Assessment
- Review Targets
- 1. Single Repository
- 2. Organization-Wide
- 3. Saved Groups
- 4. Managing Groups
Clone repo to temp directory
git clone --quiet <repo_url> /tmp/repo_review_temp
Contribution stats by author
git log --numstat --format="COMMIT|%H|%an|%ad" --date=short --since="2025-01-01" --all
Weekly breakdown
git log --format="%ad" --date=short --since="2025-01-01" | sort | uniq -c
Files touched by author
git log --author="Name" --name-only --pretty=format: | sort | uniq -c | sort -rn
File type breakdown
git log --numstat --format="" | awk '{print $3}' | grep -oE '\.[^.]+$' | sort | uniq -c | sort -rnWhat does the tools-repo-review skill do?
Comprehensive GitHub repository analysis for engineering managers with contribution stats, code quality review, team health metrics, and actionable management outputs
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill tools-repo-review --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.