codebase-inspection

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/luckybbjason1/trading --skill codebase-inspection-luckybbjason1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/luckybbjason1/trading/tree/main/.hermes/skills/github/codebase-inspection
Command: npx skills add https://github.com/luckybbjason1/trading --skill codebase-inspection-luckybbjason1

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 line-counting tools correctly, and misconfigured scans can hang on dependency directories like node_modules or .git. ## Core Features & Use Cases - Language Breakdown: Produces a summary table of files, code lines, and comment lines per programming language using pygount. - Safe Folder Exclusion: Provides ready-made --folders-to-skip patterns for Python, JavaScript, and general projects to avoid crawling dependency trees. - Flexible Output: Supports summary tables, JSON output, per-file detail, and language filtering via --suffix. - Use Case: When asked "how big is this repo?", run pygount with the recommended exclusions to get an accurate LOC and language distribution in seconds. ## Quick Start Ask the assistant 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 with pygount?

Run pygount --format=summary in the repository root with --folders-to-skip excluding .git, node_modules, and venv directories. The summary table shows files, code lines, and comment lines per language.

How to get a language breakdown of a codebase?

Use pygount --format=summary to get a per-language table with file counts, code lines, comment lines, and percentages. Filter to specific languages with --suffix, for example --suffix=py,yaml.

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 take minutes. Always pass --folders-to-skip with dependency and build directories excluded.

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 an error.

Can pygount output results as JSON for scripts?

Yes, pygount supports --format=json for programmatic consumption, alongside the default per-file format and the summary table format for human-readable reports.