codebase-inspection

Analyze repositories to report LOC, language breakdown, and code-vs-comment ratios.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/AlexiosBluffMara/mercury --skill codebase-inspection-alexiosbluffmara
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/AlexiosBluffMara/mercury/tree/main/skills/github/codebase-inspection
Command: npx skills add https://github.com/AlexiosBluffMara/mercury --skill codebase-inspection-alexiosbluffmara

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze repositories to report LOC, language breakdown, and code-vs-comment ratios.

Core Features & Use Cases

  • Provides an accurate language distribution with file counts and code vs comment metrics.
  • Produces a concise repository size and composition overview for maintenance planning.
  • Supports quick diagnostics for codebase health and engineering decisions.

Quick Start

Run the skill against a local repository to generate a full LOC, 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 count lines of code and get a language breakdown for a local repository?

You can analyze your repository to report LOC, language breakdown, and code-vs-comment ratios by running the skill against the local codebase to generate a full metrics report.

What is the best way to measure code vs comment ratios in a codebase?

Measuring code vs comment ratios in a codebase involves analyzing repository composition to distinguish code lines from comments, producing concise metrics suitable for maintenance planning and engineering decisions.

Can I exclude specific folders when calculating repository size and LOC?

Yes, the analysis supports configurable folder exclusions when calculating repository size and LOC, allowing you to skip specific directories and generate accurate codebase composition metrics.

Does pygount support language distribution analysis across multiple files?

Yes, pygount supports language distribution analysis across multiple files by providing accurate file counts and code-vs-comment metrics, delivering a concise repository size and composition overview.

How do I generate structured code metrics for downstream tooling?

Generating structured code metrics for downstream tooling requires analyzing repositories to report LOC and language breakdown, outputting structured data suitable for integration into engineering pipelines.

Why use pygount for codebase inspection instead of other code analysis tools?

Using pygount for codebase inspection enforces accurate LOC counts and language breakdowns, offering structured metrics output that distinguishes it from generic code analysis tools for maintenance planning.