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

agent-context-management.md

annual-review-process.md

accuracy-analysis.md

code-quality-catalog.md

qualitative-judgment.md

report-templates.md

production-ownership.md

historical-progress.md

Quick Reference

Critical: Context Management

Before launching ANY analysis, count commits:

git log --author="EMAIL" --after="YEAR-01-01" --before="YEAR+1-01-01" --oneline | wc -l

Batch sizing (hard limits from real failures):

Sub-tasks write to files, return 3-line summaries. Never return raw analysis inline.

Critical: Annual Review Process

7 phases, sequential:

1. Identity Discovery — find all git email variants
2. Metrics — commits, PRs, reviews, lines (git + gh CLI)
3. Read ALL Diffs — quarterly parallel sub-tasks, file-based output
4. Bug Introduction — self-reverts, crash-fixes, same-day fixes, hook bypass
5. Code Quality — anti-patterns and strengths from diff reading
6. Report Generation — structured markdown with rating + promotion assessment
7. Comparison — multi-engineer ranking with evidence

High: Accuracy Rate

Effective Accuracy = 100% - (fix-related commits / total commits)

High: Tool Separation

• Local

  git

  : ALL commit-level analysis (log, show, diff, blame, shortlog)

• gh

  CLI: ONLY for PR counts, review counts, user verification
• Never use

  gh

  to read diffs — local git is faster with no rate limits

References

Full documentation with process steps and templates in

references/

Analysis Process

annual-review-process.md

agent-context-management.md

accuracy-analysis.md

code-quality-catalog.md

Judgment & Assessment

qualitative-judgment.md

report-templates.md

Ownership & Progress

production-ownership.md

historical-progress.md

Searching References

# Find by keyword
grep -rl "accuracy" references/
grep -rl "promotion" references/
grep -rl "ownership" references/
grep -rl "anti-pattern" references/

Problem to Reference Mapping

annual-review-process.md

report-templates.md

annual-review-process.md

qualitative-judgment.md

agent-context-management.md

agent-context-management.md

qualitative-judgment.md

accuracy-analysis.md

production-ownership.md

historical-progress.md

code-quality-catalog.md

accuracy-analysis.md

production-ownership.md

historical-progress.md

Full Compiled Document

For the complete guide with all references expanded:

AGENTS.md

Usage Examples

# Annual review (single engineer)
Analyze @alice for 2025 annual review in repo org/repo.
Git email: alice@company.com. Write to ./alice-2025-review.md

# Multi-engineer comparison with promotion decision
Analyze @alice, @bob, @charlie for 2025 reviews.
I need to decide which 2 get promoted.

# Production ownership mapping
Analyze production code ownership in this repo.

# Incremental progress update
Update @alice's progress profile with latest contributions.

# Critical path risk detection
Find single points of failure in production code ownership.

# Plateau detection
Has @bob plateaued? Check last 3 quarters.