codebase-inspection

Analyze codebase size and language distribution using pygount.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill codebase-inspection-marblesodas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill codebase-inspection-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of quickly understanding how large a codebase is and what it’s made of (languages, file counts, and code-to-comment ratios) without manual counting.

Core Features & Use Cases

  • Repository LOC & language breakdown: Uses pygount to produce a per-language summary including files, code lines, and comment lines.
  • Code-vs-comment ratio analysis: Helps estimate documentation density and overall composition of a repository.
  • Practical size/scoping decisions: Supports questions like “How big is this repo?”, “What languages dominate?”, and “Which parts should we exclude from analysis?” using configurable folder and suffix filters.
  • Use Case: Reviewing a candidate repository for onboarding effort by checking language distribution and comment density, while skipping dependency and build folders to keep results accurate.

Quick Start

Ask for a repository-level summary by instructing the AI to run pygount with folder exclusions on the target repository path.

Frequently Asked Questions about codebase-inspection

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

FAQPage Schema
How do I measure lines of code and language breakdown in a git repository?

To measure lines of code and language breakdown in a git repository, use pygount to analyze the codebase. This generates a per-language summary including file counts, code lines, and comment lines while excluding dependency and build artifacts.

How do I calculate code-to-comment ratios across multiple programming languages?

Calculate code-to-comment ratios across multiple languages by running pygount on your project directory. The tool analyzes code composition and outputs documentation density metrics to help estimate overall repository quality.

How do I exclude dependency folders when scanning a codebase for code metrics?

Exclude dependency folders when scanning for code metrics by applying the --folders-to-skip filter in pygount. You can also use optional --suffix filters to narrow file types and prevent misleading or excessively long repository scans.

What is the best way to scope onboarding effort for a new codebase?

Scoping onboarding effort for a new codebase involves checking language distribution and comment density using pygount. This quickly estimates repository size and composition without manual counting, helping gauge project complexity.

Does pygount work with multiple programming languages for repository sizing?

Pygount works with multiple programming languages for repository sizing by automatically detecting file types and producing a per-language summary. It measures code lines and comment ratios across the entire project directory.

Why does my repository scan return inflated line counts?

Repository scans return inflated line counts when dependency and build artifacts are included in the analysis. Apply the --folders-to-skip parameter in pygount to exclude these directories and ensure accurate code metrics.