codebase-inspection

Analyze repository codebases to generate LOC, language breakdown, and code-vs-comment metrics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebase Inspection with pygount solves the problem of quantifying and understanding repository composition by computing LOC, language distribution, file counts, and code-vs-comment ratios.

Core Features & Use Cases

  • Basic Summary: Get a full language breakdown with file counts, code lines, and comment lines.
  • Folder Exclusions: Exclude irrelevant directories to tailor results for large repositories.
  • Language Filtering: Focus on specific languages to analyze targeted parts of the codebase.
  • Output Formats: Generate summary or JSON outputs for programmatic use.

Quick Start

Run pygount on the target repository to generate a codebase 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 a codebase to get LOC and language breakdown metrics?

To analyze a codebase for LOC and language breakdown metrics, run pygount on the target repository to generate a summary report containing code lines, comment lines, and file counts across various programming languages.

What is the best way to exclude irrelevant folders when running a repository code analysis?

The best way to exclude irrelevant folders during repository code analysis is to apply folder exclusions, which tailors the pygount results to skip non-essential directories and focus on targeted parts of large repositories.

Does pygount support JSON output for programmatic codebase analysis consumption?

Yes, pygount supports JSON output for programmatic codebase analysis consumption, allowing you to generate structured data outputs alongside standard summary reports for automated audits and quality assessments.

Can I filter static analysis metrics to focus on specific languages in my codebase?

Yes, you can filter static analysis metrics to focus on specific languages in your codebase, enabling targeted analysis of individual language components within mixed-language software projects.

Do I need pygount installed to perform code-vs-comment ratio analysis on a repository?

Yes, you need pygount installed to perform code-vs-comment ratio analysis on a repository, as it is the required dependency for computing these specific codebase metrics and generating reports.