contributor-codebase-analyzer

Analyze commit diffs to surface contributor insights and codebase governance.

6|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/anivar/contributor-codebase-analyzer --skill contributor-codebase-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contributor-codebase-analyzer
Source: https://github.com/anivar/contributor-codebase-analyzer/tree/main
Command: npx skills add https://github.com/anivar/contributor-codebase-analyzer --skill contributor-codebase-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Contributor reviews and governance insights rely on understanding changes across every commit and the broader health of the codebase. This Skill provides a reproducible, checkpointed workflow that reads every commit diff, surfaces qualitative judgment, and maps codebase governance data for informed decisions.

Core Features & Use Cases

  • Reads every commit diff for each contributor to surface accuracy baselines, anti-patterns, and growth signals.
  • Maps repository structure, cross-repo relationships, and governance information to support enterprise code health.
  • Generates growth-oriented performance reviews with concrete evidence from code changes and governance data.
  • Supports GitHub and GitLab environments with incremental saving and resume-capable workflows.

Quick Start

Run onboarding to initialize detection and configuration.

Frequently Asked Questions about contributor-codebase-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze commit diffs for a contributor performance review?

You can analyze commit diffs by running the Contributor mode, which reads every commit diff per contributor to surface accuracy baselines, anti-patterns, and growth signals for evidence-based performance reviews.

Can I map codebase governance and cross-repo relationships across GitHub and GitLab?

Yes, Codebase mode maps repository structure, cross-repo relationships, and governance information across GitHub and GitLab ecosystems to support enterprise code health monitoring.

Do I need git and gh or glab installed to analyze codebase governance data?

Yes, you need git and either gh or glab installed. The Skill relies on local git reads for performance and safety, using these CLI tools to access commit diffs and governance data.

What is the best way to resume a large codebase analysis if it gets interrupted?

The best way to resume interrupted codebase analysis is using its incremental checkpoint feature. The Skill saves progress incrementally via checkpoints, enabling resume-capable workflows without losing prior analysis state.

How does checkpointed diff reading work for long-running contributor reviews?

Checkpointed diff reading works by saving analysis progress incrementally as it reads every commit diff. This ensures long-running contributor reviews can be paused and resumed safely without losing previously surfaced insights.

Are there limitations when using local git reads for cross-repo governance mapping?

A limitation is that it requires local repository clones and appropriate CLI access. It prioritizes local git reads for performance and safety, meaning remote-only or inaccessible repositories cannot be analyzed.