codebase-inspection

Count lines of code and classify repository content by language.

3|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill codebase-inspection-twjarviszyra-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/twjarviszyra-web/hermes-unbound/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill codebase-inspection-twjarviszyra-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of estimating repository size and composition by producing reliable lines-of-code metrics, language breakdowns, and code-versus-comment ratios.

Core Features & Use Cases

  • Repository Metrics: Summarize file counts, code lines, comment lines, and language distribution across a codebase.
  • Codebase Audits: Quickly assess how large a project is and which languages dominate it before planning refactors or reviews.
  • Use Case: A maintainer can inspect a GitHub repository to compare Python, JavaScript, and Markdown usage and identify how much of the tree is source code versus documentation.

Quick Start

Ask for a pygount-based inspection of the repository to get a language summary, LOC totals, and code-versus-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 count lines of code and get a language breakdown for a GitHub repository?

You can count lines of code and get a language breakdown by running a pygount-based inspection on the repository. This produces reliable summary metrics across source trees, including total lines of code, file counts, and language distribution.

How do I calculate the code-versus-comment ratio in my codebase?

To calculate the code-versus-comment ratio, apply a pygount-based codebase inspection to your source tree. It classifies repository content by language and outputs distinct counts for source code lines and comment lines.

Does pygount automatically exclude dependency directories when sizing a repository?

Pygount requires excluded dependency directories to produce reliable repository sizing metrics. You must configure these exclusions during the codebase inspection to ensure generated LOC totals and language breakdowns reflect only your source code.

What is the best way to audit a codebase before planning a refactor?

The best way to audit a codebase before a refactor is to measure repo size and language mix. A quick codebase inspection identifies which languages dominate the project and how much of the tree is source code versus documentation.

Can I analyze the language composition of a local source tree instead of a GitHub project?

Yes, you can analyze local source trees. The codebase inspection uses pygount to apply language composition checks and code-versus-comment analysis across any repository content, not just GitHub projects.

Why do my repository metrics show inflated lines of code?

Repository metrics show inflated lines of code when dependency directories are not excluded. Applying pygount with excluded dependency directories ensures the codebase audit produces reliable summary metrics for your actual source tree.