codebase-inspection

Analyze repositories to quantify size, language distribution, and code-vs-comment ratios.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly quantify codebase size, language distribution, and code-vs-comment ratios to understand repository health and maintenance needs.

Core Features & Use Cases

  • Language breakdown with file counts, code lines, and comment lines.
  • Exclude noisy directories via configurable folders-to-skip for accurate metrics.
  • Filter results by language or file type to focus on specific areas.
  • Get per-file breakdowns to identify hotspots and technical debt.

Quick Start

Run pygount on your repository with appropriate folder exclusions to generate a language breakdown and code-vs-comment report.

Frequently Asked Questions about codebase-inspection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze repository code size and language distribution?

Analyze repository code size and language distribution by running pygount to quantify total lines of code, language breakdown, and file counts. The tool generates a detailed report showing codebase composition across all detected programming languages.

Can I exclude noisy directories when calculating code metrics?

You can exclude noisy directories when calculating code metrics using configurable folders-to-skip. This ensures accurate metrics by filtering out vendor, build, or dependency folders that would otherwise skew your lines of code and language distribution analysis.

How do I get a per-file code and comment breakdown to identify technical debt?

Get a per-file code and comment breakdown to identify technical debt by running pygount with detailed analysis enabled. This highlights individual file hotspots showing exact code lines, comment lines, and code-vs-comment ratios for targeted maintenance.

What's the best way to measure code-vs-comment ratios in a monorepo?

Measure code-vs-comment ratios in a monorepo by applying pygount to the repository root with appropriate folder exclusions. This scales to large monorepos, assessing overall codebase composition and maintenance readiness across mixed languages.

Can I filter code analysis results by specific programming language?

You can filter code analysis results by specific programming language or file type to focus on targeted areas. This allows you to isolate metrics for individual languages within a mixed codebase for focused maintenance assessment.

Does pygount work without external dependencies for codebase inspection?

Pygount works for codebase inspection without external component dependencies listed in its configuration. It relies on pygount internally to perform language breakdown, count lines of code, and generate comment counts for repository health analysis.