codebase-inspection

Inspect repositories with pygount to count lines of code and analyze language composition.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill codebase-inspection-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill codebase-inspection-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pygount.

What problem does it solve? Answering questions about repository size, language breakdown, and code-versus-comment ratios normally requires manual counting or ad-hoc scripts. This Skill provides ready-to-use pygount commands that produce accurate codebase statistics without crawling dependency folders or hanging on large trees. ## Core Features & Use Cases - LOC and Language Breakdown: Generate summary tables showing file counts, code lines, and comment lines per programming language. - Targeted Analysis: Filter scans by file suffix to count only specific languages, or produce per-file and JSON output for programmatic use. - Safe Defaults: Built-in folder exclusion patterns prevent pygount from scanning .git, node_modules, and virtual environments. - 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 per-language code and comment breakdown in seconds. ## Quick Start Use the codebase-inspection skill to count the lines of code and show the language breakdown of this repository.

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

How to count only Python files with pygount?▼

Use the --suffix flag to filter by extension, for example pygount --suffix=py --format=summary. You can list multiple suffixes such as py,yaml,yml to count several languages in one pass.

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. Add --folders-to-skip with the appropriate exclusions for your project type to avoid this.

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

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

Can pygount output results as JSON for scripts?▼

Yes, pass --format=json to get machine-readable output suitable for programmatic processing. The default summary format is better for human-readable tables, while the default per-file format supports sorting by code lines.