codebase-inspection

Analyze codebases for LOC counts, language distribution, and code-vs-comment ratios.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11 --skill codebase-inspection-cloudliness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11 --skill codebase-inspection-cloudliness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect and analyze codebases to measure lines of code, language distribution, and code-vs-comment ratios using pygount, enabling data-driven code quality and repo management.

Core Features & Use Cases

  • LOC counting: Compute total lines of code and comments across a repository while excluding common artifacts.
  • Language breakdown: Provide per-language counts and percentages to understand code composition.
  • Code-vs-comment ratio: Report the balance between code and comments to assess documentation effort.
  • Use Case: When planning refactors, perform a quick stats pass on a new project or PR to guide priorities.

Quick Start

Scan the target directory to generate LOC, language, and code-vs-comment metrics.

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 analyze language distribution in a repository?▼

To count lines of code and analyze language distribution, scan the target directory to generate LOC counts, per-language percentages, and code-vs-comment ratios. This uses pygount to compute metrics while excluding common artifacts, returning structured outputs for dashboards or repo audits.

What is a code-vs-comment ratio and when do I need to calculate it?▼

A code-vs-comment ratio measures the balance between executable lines and documentation within a codebase. You need to calculate it during code quality reviews or onboarding to assess documentation effort and guide refactoring priorities across single repositories or multi-repo portfolios.

Can I use pygount to analyze code composition across multiple repositories?▼

Yes, you can use pygount to analyze code composition across multi-repo portfolios. The tool computes per-language counts and percentages, supporting CLI-based usage to deliver reproducible reports and structured outputs suitable for dashboard integration.

Does the codebase inspection process exclude build artifacts from LOC metrics?▼

Yes, the codebase inspection process excludes common artifacts when computing total lines of code and comments. It relies on pygount to measure actual source code composition, ensuring accurate language breakdowns and code-vs-comment ratios for data-driven repo management.

What's the best way to generate reproducible LOC reports for a new project?▼

The best way to generate reproducible LOC reports is using CLI-based analysis to scan the target directory. This delivers structured outputs with lines of code, language distribution, and code-vs-comment metrics, enabling data-driven code quality assessments for onboarding new projects.