codebase-inspection

Compute repository size metrics with pygount, including LOC, language distribution, and file counts.

Updated May 15, 2026
One-click install
npx skills add https://github.com/cabezno/bmb-encover-agent --skill codebase-inspection-cabezno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/cabezno/bmb-encover-agent/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/cabezno/bmb-encover-agent --skill codebase-inspection-cabezno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand how large a codebase is and what it is made of, including lines of code, language breakdown, and code-vs-comment ratios.

Core Features & Use Cases

  • Language breakdown & file counts: Identify which languages dominate a repository and how many files each includes.
  • LOC and documentation ratios: Measure code lines vs comment/docs lines to estimate readability and maintainability signals.
  • Actionable reporting: Produce human-readable summaries or machine-friendly JSON for further analysis.
  • Use Case: You are evaluating whether to modernize or audit a legacy repo and need a fast answer about size, language mix, and documentation density before committing time.

Quick Start

Run the codebase inspection on the target repository directory to get a summarized LOC and language breakdown using pygount.

Frequently Asked Questions about codebase-inspection

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

FAQPage Schema
How do I get a language breakdown and lines of code count for a repository?▼

To get a language breakdown and lines of code count for a repository, run a codebase inspection to extract file counts, language distribution, and code-to-comment ratios using pygount. It quickly quantifies project size and composition for mixed-language codebases.

What is the best way to measure code-to-comment ratios across a monorepo?▼

Measuring code-to-comment ratios across a monorepo requires analyzing code lines versus documentation lines to estimate readability. A codebase inspection calculates these documentation density metrics using pygount to help estimate maintainability.

Can I export lines of code metrics as JSON output for further analysis?▼

Yes, you can export lines of code metrics as JSON output. The codebase inspection supports machine-friendly JSON output formats alongside human-readable summaries, allowing you to easily integrate repository metrics into downstream analysis pipelines.

Does pygount support skipping specific folders when analyzing repository size?▼

Yes, pygount supports skipping specific folders when analyzing repository size. The codebase inspection execution requires configuring appropriate folders-to-skip parameters to ensure accurate lines of code and language distribution metrics.

When do I need to quantify repo size and composition for a legacy codebase?▼

You need to quantify repo size and composition for a legacy codebase when evaluating modernization, refactoring, or auditing tasks. Extracting lines of code and language breakdown helps assess project scope and documentation density before committing time.