codebase-inspection

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

1|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/agtktID/indagis-agent --skill codebase-inspection-agtktid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/agtktID/indagis-agent/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/agtktID/indagis-agent --skill codebase-inspection-agtktid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pygount.

What problem does it solve? Answering questions about repository size and composition normally requires manual counting or ad-hoc scripts. This Skill provides ready-to-use pygount commands that produce accurate lines-of-code counts, language breakdowns, and code-vs-comment ratios for any codebase. ## Core Features & Use Cases - Language Breakdown Summaries: Generate per-language file counts, code lines, and comment lines with a single pygount summary command. - Smart Directory Exclusion: Prebuilt --folders-to-skip patterns for Python, JavaScript, and general projects prevent pygount from crawling .git, node_modules, and virtual environments. - Language Filtering and JSON Output: Restrict analysis to specific file suffixes or emit JSON for programmatic consumption. - Use Case: A user asks how large a monorepo is and what languages it contains. Run the summary command with proper exclusions and report the language percentages, total LOC, and comment ratios in seconds. ## Quick Start Use the codebase-inspection skill to analyze this repository and give me a language breakdown with total lines of code.

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 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 completes quickly.

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

Use pygount --format=summary . to produce a table showing each detected language with file counts, code lines, comment lines, and percentage of total. Filter to specific languages with --suffix, for example --suffix=py for Python only.

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

Pygount crawls every directory by default, including .git, node_modules, and virtual environments, which can contain millions of files. Pass --folders-to-skip with dependency and build directories to limit the scan to actual source code.

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

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

Can pygount output results as JSON for scripts?▼

Yes, pygount supports --format=json for programmatic consumption alongside the default per-file listing and the summary table format. JSON output is useful when feeding metrics into dashboards or other tooling.

What are the limitations of pygount for code metrics?▼

Pygount may count JSON lines conservatively, so use wc -l for accurate JSON counts. Very large monorepos scan slowly, so target specific languages with --suffix instead of scanning everything.