codebase-inspection

Analyze repository lines of code, language breakdown, and comment ratios using pygount.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill codebase-inspection-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/loteiron/ZeusAgent/tree/main/skills/software-development/codebase-inspection
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill codebase-inspection-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pygount.

What problem does it solve? Answering questions about repository size, language composition, and code-to-comment ratios requires running the right counting tool with the right exclusions; doing it manually or with naive commands like wc -l produces misleading numbers by including dependencies and build artifacts. ## Core Features & Use Cases - Language Breakdown Summaries: Run pygount summary reports showing file counts, code lines, and comment lines per language. - Dependency-Aware Scanning: Exclude .git, node_modules, venv, and build directories so scans stay fast and accurate. - Targeted Language Filtering: Restrict counts to specific file suffixes such as py, yaml, or yml for focused analysis. - Use Case: A user asks "how big is this repo and what languages does it use?" The agent runs pygount with proper folder exclusions and returns a per-language table of files, code, and comment lines. ## Quick Start Use the codebase-inspection skill to give me a language breakdown and total lines of code for this repository, excluding node_modules and virtual environments.

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 in a repository?▼

Run pygount with the summary format from the repository root to get per-language file counts, code lines, and comment lines. Always pass --folders-to-skip to exclude .git, node_modules, and virtual environments so the scan stays fast.

How to get a language breakdown of a codebase with pygount?▼

Use pygount --format=summary with folder exclusions to produce a table listing each detected language with its file count, code lines, comment lines, and percentage of the total. Add --suffix to filter specific languages.

Why does pygount hang or take a long time on my repo?▼

Pygount crawls every directory by default, including node_modules, .git, and virtual environments, which can contain millions of files. Pass --folders-to-skip with dependency and build directories to keep scans fast.

Why does Markdown show zero code lines in pygount output?▼

Pygount classifies all Markdown content as comments rather than code, so Markdown files report zero code lines. This is expected behavior, not a bug in the scan.

Can pygount count only specific languages like Python?▼

Yes, use the --suffix flag to restrict counting, for example --suffix=py for Python only or --suffix=py,yaml,yml for multiple types. This also speeds up scans on large monorepos.

What are the limitations of pygount for line counting?▼

Pygount counts JSON lines conservatively, so wc -l is more accurate for JSON files. It also labels files as pseudo-languages like __generated__, __duplicate__, or __unknown__, which may need interpretation in the summary.