codebase-inspection

Analyze codebases with pygount to quantify LOC, language distribution, and code-vs-comment ratios.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pygount.

What problem does it solve?

Codebases can be large and heterogeneous; this Skill provides measurable insights into repository composition using pygount to guide maintenance and decisions.

Core Features & Use Cases

  • LOC & Language Breakdown: Calculates lines of code per language and counts files per language.
  • Code/Comment Ratios: Reports the balance between code and comments for complexity assessment.
  • Use Case: Use this to quickly assess a project before refactoring, onboard new contributors, or compare multiple repositories.

Quick Start

Run pygount on your repository to generate a language breakdown, file counts, and code-vs-comment ratios.

Frequently Asked Questions about codebase-inspection

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

FAQPage Schema
How do I get a language breakdown and LOC count for a codebase?

To get a language breakdown and LOC count for a codebase, this Skill analyzes your repository path using pygount to calculate lines of code per language and count files per language. It provides a structured summary of repository composition.

What is a code-to-comment ratio and how does it help with repository audits?

A code-to-comment ratio measures the balance between executable code and comments to assess complexity. During a repository audit, reporting this ratio helps guide maintenance decisions and evaluate codebase composition across directories.

Can I analyze multiple repositories for cross-project comparisons?

Yes, you can perform cross-project comparisons by running analysis on multiple repositories. The Skill calculates repository metrics including language distribution and file counts for each target path, enabling direct comparison across heterogeneous codebases.

Does this code analysis tool work with all programming languages?

The code analysis works across languages and directories, leveraging pygount to identify language distribution and count files per language. It supports heterogeneous codebases for comprehensive project audits and onboarding assessments.

Do I need pygount installed to calculate lines of code?

Yes, you need pygount installed and a target path to your repository to calculate lines of code. This dependency is required for the Skill to quantify LOC, language distribution, and code-vs-comment ratios.