codebase-inspection

Inspect repositories with pygount to report LOC, language breakdown, and code-to-comment ratios.

Updated Aug 21, 2026

Search Tags:#codebase analysis #code metrics #pygount #language breakdown #lines of code #repository inspection

Ready to run

npx skills add https://github.com/ewtodd/son-of-anton --skill codebase-inspection-ewtodd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/ewtodd/son-of-anton/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/ewtodd/son-of-anton --skill codebase-inspection-ewtodd

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, and naive scans crawl dependency directories and hang. ## Core Features & Use Cases - Language Breakdown: Produces a summary table of files, code lines, and comment lines per programming language using pygount. - Folder Exclusion Patterns: Provides ready-made --folders-to-skip lists for Python, JavaScript, and general projects to avoid scanning .git, node_modules, and venv. - Language Filtering and Output Formats: Supports --suffix filtering for specific languages and summary or JSON output for programmatic use. - Use Case: When asked "how big is this repo", run pygount with the catch-all exclusion list and report the summary table with per-language percentages. ## Quick Start Ask the agent to count the lines of code and show the language breakdown of the current repository 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 count lines of code in a repository?▼

Run pygount with --format=summary from the repository root to get a per-language table of files, code lines, and comment lines. Always pass --folders-to-skip to exclude .git, node_modules, and virtualenv directories.

How do I get a language breakdown of a codebase?▼

Use pygount --format=summary, which groups results by detected language with file counts, code lines, comment lines, and percentages. Use --suffix=py,yaml to restrict the breakdown to specific languages.

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

Pygount crawls every directory by default, including .git, node_modules, and venv, which can take minutes on large dependency trees. Pass --folders-to-skip with those directories excluded to keep scans fast.

Why does pygount show zero code lines for Markdown files?▼

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

Can pygount output results as JSON for scripts?▼

Yes, pygount supports --format=json for programmatic consumption in addition to the default summary table. For accurate raw line counts of JSON files themselves, use wc -l directly since pygount counts JSON conservatively.