skills.rest
azmiariffaris
azmiariffarisCOMMUNITY
Explore all skills by this author →
GitHub

codebase-inspection

Count lines of code and language breakdowns using pygount.

Updated Aug 27, 2026
Search Tags:#codebase#loc#code-metrics#language-analysis#pygount#repository-insights
One-click install
npx skills add https://github.com/azmiariffaris/HERMES-AGENT --skill codebase-inspection-azmiariffaris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-inspection
Source: https://github.com/azmiariffaris/HERMES-AGENT/tree/main/snapshot/hermes/skills/github/codebase-inspection
Command: npx skills add https://github.com/azmiariffaris/HERMES-AGENT --skill codebase-inspection-azmiariffaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps developers quickly quantify and understand codebases by producing LOC counts, language breakdowns, and code-vs-comment ratios, enabling better project assessment and planning.

Core Features & Use Cases

  • LOC and language breakdown by file type
  • Code-vs-comment ratio analysis across repositories
  • Use Case: Assess a repo to estimate complexity and identify hotspots for refactoring

Quick Start

Analyze a repository at /path/to/repo to get a language and LOC overview and generate a summary.

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 breakdown in a repository?▼

To count lines of code and analyze language breakdown, the tool uses pygount to scan your repository and compute per-language metrics. It outputs a concise summary revealing the LOC distribution and code-vs-comment ratios for your project.

What is code-vs-comment ratio analysis and when do I need it for a codebase?▼

Code-vs-comment ratio analysis measures the proportion of actual code to comments across a codebase. You need this during software audits or repo assessments to estimate complexity, identify hotspots for refactoring, and track project size over time.

Can I use this to assess a repository for complexity and refactoring hotspots?▼

Yes, you can assess a repository for complexity and refactoring hotspots by analyzing the codebase. It quantifies LOC and language breakdown by file type, helping you identify large or complex areas that may require refactoring.

Does the codebase analysis require any dependencies or specific environment setup?▼

No specific environment setup or dependencies are required to use this codebase analysis tool. It operates independently to scan your repository path and generate a language and LOC overview summary suitable for automation.

What's the best way to track codebase size and language mix over time?▼

The best way to track codebase size and language mix over time is by running this analysis periodically. It uses pygount to compute per-language metrics and outputs a concise summary, allowing you to compare languages and track repository growth.

Are there limitations when using pygount for repository language analysis?▼

Limitations of using pygount for repository language analysis include its focus on quantitative metrics like LOC and code-vs-comment ratios. It provides a concise summary for automation but does not perform qualitative code analysis or identify logical errors.

Related Skills

Explore More Software Engineering Skills→
X-School-AcademyX-School-Academy
9

dev-swarm-install-ai-code-agent

Install AI code agent CLI tools via npm, install script, or Homebrew.

Official
Advanced
Monjyu1101Monjyu1101
1

codebase-inspection

Analyze codebases with pygount to produce LOC, language breakdown, and file counts.

Community
Intermediate
archibatearchibate
6

code-quality-metrics

Measure code complexity and quality metrics across multi-language repositories.

Community
Intermediate
otrebuotrebu
4

analyze-size

Analyze codebases with cloc to compute total lines of code and language distribution.

Community
Intermediate