codebase-inspection

Analyze repository code size and language composition with pygount.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill codebase-inspection-titoprausee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/github/codebase-inspection
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill codebase-inspection-titoprausee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from understanding how large a codebase is, what languages it uses, and how much of it is actual code versus comments or empty files.

Core Features & Use Cases

  • LOC and Size Analysis: Count lines of code across an entire repository for quick size estimates.
  • Language Breakdown: Identify how many files and lines belong to each language in a mixed codebase.
  • Code Quality Snapshot: Compare code, comment, and empty-file ratios to understand how much of the repo is implementation versus documentation or scaffolding.
  • Use Case: A maintainer can inspect a monorepo before planning refactors, budgeting review time, or comparing the footprint of different services.

Quick Start

Ask the assistant to analyze the repository with the codebase-inspection skill and return the lines of code, language breakdown, and code-versus-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 across a mixed-language codebase?

To count lines of code across a mixed-language codebase, the skill analyzes repository composition to provide total LOC and a per-language file and line breakdown.

What is the best way to measure code versus comment ratios in a repository?

Measuring code versus comment ratios involves comparing implementation lines against documentation and empty files, producing a quick code quality snapshot of the repository.

Does pygount support folder exclusion to skip dependency trees during repository metrics analysis?

Yes, pygount supports folder exclusion handling, ensuring accurate repository metrics by skipping dependency trees during the lines of code and language breakdown analysis.

Can I analyze a monorepo's language breakdown before planning a refactor?

Yes, you can analyze a monorepo's language breakdown to identify file and line counts per language, helping estimate the footprint of different services before planning refactors.

Why does my code analysis include dependency files in the language breakdown?

Code analysis may include dependency files if folder exclusion is not applied, which is why this skill requires folder exclusion handling to produce accurate summaries without scanning dependency trees.