codebase-inspection

Analyze codebases with pygount to report LOC, language breakdown, and code-vs-comment ratios.

26|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/TeamSloppy/Sloppy --skill codebase-inspection-teamsloppy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/TeamSloppy/Sloppy/tree/main/Sources/sloppy/Resources/Skills/codebase-inspection
Command: npx skills add https://github.com/TeamSloppy/Sloppy --skill codebase-inspection-teamsloppy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly understand codebase composition by counting lines of code, identifying languages, and evaluating code-to-comment ratios across a repository.

Core Features & Use Cases

  • LOC and language breakdown: get per-language file counts and code vs. comment distribution.
  • Repository sizing for planning: estimate project scope for onboarding, audits, or refactors.
  • Use Case: When asked "how big is this repo?" quickly assemble a language profile and LOC totals to inform decisions.

Quick Start

Run this skill against a repository to generate a pygount-based report on languages, counts, and 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 a repository?

To count lines of code and get a language breakdown, analyze the repository to report per-language file counts and code-vs-comment distribution. This produces a structured summary of project scope and language diversity.

What is a code-to-comment ratio and when do I need to evaluate it?

A code-to-comment ratio measures the proportion of comment lines to executable code in a repository. You need to evaluate it when assessing documentation quality, maintenance effort, or onboarding complexity for software projects.

Do I need pygount installed to analyze codebase composition and LOC metrics?

Yes, you need pygount installed to analyze codebase composition and LOC metrics. The tool relies on this dependency to read the repository and produce a structured summary of languages, counts, and ratios.

Can I use repository sizing to estimate project scope for refactoring or audits?

Yes, you can use repository sizing to estimate project scope for refactoring or audits. By assembling a language profile and LOC totals, you quickly understand codebase composition to inform maintenance and onboarding decisions.

What's the best way to measure language diversity across large software repositories?

The best way to measure language diversity across large software repositories is to analyze codebases with pygount, which processes repositories of any size and reports per-language file counts alongside code-vs-comment ratios.