skills.rest
AvaTar-ArTs
AvaTar-ArTsCOMMUNITY
Explore all skills by this author →
GitHub

codebase-inspection

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

Updated Jul 10, 2026
Search Tags:#codebase analysis#code metrics#pygount#language breakdown#lines of code#repository inspection
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill codebase-inspection-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill codebase-inspection-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pygount.

What problem does it solve? Answering questions about repository size and composition—lines of code, language distribution, and comment ratios—requires running the right counting tool with the right exclusions, which is easy to get wrong on large codebases. ## Core Features & Use Cases - Language Breakdown: Produces a summary table of files, code lines, and comment lines per programming language using pygount. - Targeted Scans: Filters by file suffix and skips dependency folders like node_modules, .git, and venv to keep scans fast. - Multiple Output Formats: Supports summary tables and JSON output for programmatic consumption. - Use Case: When asked "how big is this repo?", run a pygount summary with proper folder exclusions to report total LOC, dominant languages, and code-to-comment ratios in seconds. ## Quick Start Ask the AI to inspect the current repository with pygount and report the lines of code and language breakdown, excluding dependency folders.

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 do I get a language breakdown of a codebase?▼

Use pygount --format=summary to produce a table showing each detected language with file counts, code lines, comment lines, and percentage of total. Add --suffix=py,yaml to restrict the breakdown to specific languages.

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

Pygount crawls every directory by default, including node_modules, .git, and virtual environments, which can contain thousands of files. Exclude them with --folders-to-skip, and on repos with 3,000+ files scan targeted subdirectories instead of the full tree.

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.

What are the limitations of pygount for large monorepos?▼

Pygount can time out on repositories with thousands of files even with exclusions and suffix filters. Fall back to scanning individual subdirectories, using find with wc -l for file counts, or sampling files for LOC estimates instead of retrying the full scan.

Related Skills

Explore More Software Engineering Skills→
sanjanbsanjanb
1

clonedeps

Clone dependency source repositories into an ignored local workspace for agent inspection.

Community
Intermediate
StarryCodStarryCod
11

codebase-inspection

Compute line counts, language distribution, and code-vs-comment ratios with pygount.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

discover

Assess project health, architecture, and risks in existing codebases.

Community
Intermediate
juliuss1907juliuss1907

codebase-inspection

Analyze codebases with pygount to calculate LOC and language composition.

Community
Intermediate