Agent skill · Code Review & Quality

contributor-analyzer

Analyzes engineering contributors for annual reviews, progress tracking, and production ownership. Reads every commit diff (not sampling), calculates accuracy rates, assesses engineering maturity through qualitative judgment, and generates promotion-ready performance reviews. Works with any git repository using local git for commit analysis and gh CLI for GitHub PR/review metadata.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill contributor-analyzer-anivar-contributor-analyzer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.0
Declared author: anivar
Requires: Requires git (local repository access) and gh (GitHub CLI) for full analysis. Optional: jq for JSON parsing, bc for…
Path: skills/analysis/contributor-analyzer-anivar-contributor-analyzer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Contributor Analyzer Unified skill for engineering contributor analysis. Combines annual review generation, historical progress tracking, production ownership mapping, and qualitative judgment — all driven by reading actual commit diffs. ## Skill Format Each reference file covers one analysis concern: - **Quick Reference**: Summary tables and key thresholds - **Process Steps**: Bash commands and orchestration - **Templates**: Output formats for reports and profiles - **Deep Dive**: Full context with examples from real-world 1,091-commit analysis **Impact ratings**: CRITICAL (blocks accuracy), HIGH (major insight), MEDIUM (enriches analysis) ## When to Apply Reference these guidelines when: - Running annual or quarterly performance reviews - Assessing promotion readiness with evidence - Tracking contributor progress over time (incremental updates) - Mapping production code ownership and risk - Comparing multiple engineers for team decisions - Identifying single points of failure in codebase ownership ## Priority-Ordered References | Priority | Reference | Impact | Description | |----------|-----------|--------|-------------| | 1 | `agent-context-management.md` | CRITICAL | Batch s

What's inside
Steps it walks through
  1. Skill Format
  2. When to Apply
  3. Priority-Ordered References
  4. Quick Reference
  5. Critical: Context Management
  6. Critical: Annual Review Process
  7. High: Accuracy Rate
  8. High: Tool Separation
  9. References
  10. Analysis Process
  11. Judgment & Assessment
  12. Ownership & Progress
  13. Searching References
  14. Problem to Reference Mapping
Ships with 1 file
  • metadata.json
Commands it runs
git log --author="EMAIL" --after="YEAR-01-01" --before="YEAR+1-01-01" --oneline | wc -l
Find by keyword
grep -rl "accuracy" references/
grep -rl "promotion" references/
grep -rl "ownership" references/
grep -rl "anti-pattern" references/
More from claude-skill-registry
All skills →
About this skill
What does the contributor-analyzer skill do?

Analyzes engineering contributors for annual reviews, progress tracking, and production ownership. Reads every commit diff (not sampling), calculates accuracy rates, assesses engineering maturity through qualitative judgment, and generates promotion-ready performance reviews. Works with any git repository using local git for commit analysis and gh CLI for GitHub PR/review metadata.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill contributor-analyzer-anivar-contributor-analyzer --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.

Keep going