codebase-inspection

Analyze codebases with pygount to produce LOC counts and language breakdowns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly quantify and understand a codebase by computing lines of code, language distribution, and code-vs-comment ratios using pygount.

Core Features & Use Cases

  • LOC counting and language breakdown for repositories of any size.
  • Code-vs-comment ratios to assess documentation and clarity.
  • Repo health indicators such as file counts and language balance to inform refactoring decisions.
  • Use Case: When asked "how big is this repo" or "what languages dominate this project," run this Skill to surface actionable metrics.

Quick Start

Run pygount on your repository to generate a detailed LOC count, language breakdown, and code-vs-comment ratios.

Frequently Asked Questions about codebase-inspection

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

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

To count lines of code and get a language breakdown, analyze the codebase with pygount to generate summary metrics and per-language breakdown. This delivers LOC counts and language distribution for repositories of any size.

What is a code-vs-comment ratio and how does it assess codebase health?

A code-vs-comment ratio measures the proportion of comments relative to executable code lines. Analyzing this ratio helps assess documentation clarity and codebase health, indicating whether a project has sufficient explanatory comments for maintainability.

Can I exclude noisy directories when analyzing a repository's language composition?

Yes, you can exclude noisy directories when analyzing a repository's language composition. The codebase analysis executes pygount while excluding specified noisy directories to ensure accurate repo stats and reliable lines of code counts.

Does pygount provide JSON output for codebase metrics and LOC counts?

Yes, pygount provides JSON output for codebase metrics and LOC counts. The codebase analysis optionally produces JSON formatted results containing summary metrics, file counts, and per-language breakdowns for integration into other tools.

What's the best way to measure repo size and language balance for refactoring decisions?

The best way to measure repo size and language balance is to analyze codebases with LOC counting and language distribution metrics. These repo health indicators quantify file counts and language composition to inform refactoring decisions.

Why does my codebase analysis show unexpected language composition results?

Unexpected language composition results during codebase analysis often occur when noisy directories are included. Excluding build artifacts and vendor files from your repository before running pygount ensures the language breakdown reflects your actual source code.