codebase-inspection

Count lines of code and report language breakdowns with pygount.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gqf2008/hermez-ai --skill codebase-inspection-gqf2008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/gqf2008/hermez-ai/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/gqf2008/hermez-ai --skill codebase-inspection-gqf2008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect and quantify codebases by providing LOC, language breakdown, and code-vs-comment ratios to aid estimation, refactoring, and quality analysis.

Core Features & Use Cases

  • LOC counting with per-language totals and file counts.
  • Language breakdown showing primary languages and distribution.
  • Code-vs-comment ratio to understand documentation vs actual code.
  • Use cases include prior to refactoring, onboarding new contributors, and repository audits.

Quick Start

Compute a per-language summary and code-vs-comment ratios by running pygount on the target repository with an appropriate --folders-to-skip list.

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 and get a language breakdown for my repository?

You can count lines of code and get a language breakdown by running pygount on your target repository, which generates per-language totals, file counts, and language distribution metrics.

What is the code-to-comment ratio and how does pygount calculate it?

The code-vs-comment ratio measures documentation versus actual code. Pygount calculates this by analyzing file-level metrics across multiple languages to help assess documentation density and codebase quality.

Can I skip specific folders when analyzing codebase metrics?

Yes, you can skip specific folders when analyzing codebase metrics. The Skill supports pygount options like --folders-to-skip and --format, allowing you to exclude directories and generate reproducible insights.

Does pygount support per-language aggregation for repositories with multiple languages?

Yes, pygount supports per-language aggregation for repositories with multiple languages. It provides language breakdowns showing primary languages and distribution to deliver reproducible codebase insights.

When should I run a codebase inspection for LOC and comment ratio analysis?

You should run a codebase inspection for LOC and comment ratio analysis prior to refactoring, when onboarding new contributors, or during repository audits to aid project estimation and quality analysis.

What is the best way to audit a codebase using lines of code and comment ratios?

The best way to audit a codebase is to compute a per-language summary and code-vs-comment ratios by running pygount with an appropriate --folders-to-skip list, yielding file-level metrics across multiple languages.