Contributor Codebase Analyzer

What it does

The Contributor Codebase Analyzer reads every commit diff within a codebase, quarterly, to assess engineering contributions beyond simple volume metrics. It calculates an accuracy baseline for shipped code, detects design improvements and anti-patterns, and maps codebase structure while identifying technical debt. The skill generates growth reviews with specific evidence from commits, avoiding scores or rankings.

When to use it

• Identify hidden contributors: Discover engineers who simplify complexity rather than adding to it, potentially overlooked by traditional metrics.
• Improve code quality: Detect recurring anti-patterns and areas of technical debt within the codebase.
• Inform growth reviews: Provide specific commit evidence for engineering performance discussions, moving beyond generic feedback.
• Understand dependencies: Map cross-repository dependencies to improve architectural understanding.

Key capabilities

• Reads every commit diff quarterly
• Calculates an accuracy baseline (code shipped without fixes)
• Detects design improvements and anti-patterns
• Maps codebase structure, cross-repo dependencies, and technical debt
• Generates growth reviews with specific commit evidence

Example prompts

• "Analyze the contributions of [engineer's name] in the last quarter."
• "Show me areas of the codebase with recurring design anti-patterns."
• "Generate a report on cross-repository dependencies for the payment processing module."

Tips & gotchas

The skill requires access to a Git or GitLab repository. Analysis is incremental and saves progress, allowing for interruptions and resume later due to agentic context limits.