codebase-stats

Collect codebase metrics and debt indicators across multiple languages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill codebase-stats
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-stats
Source: https://github.com/ribatshepo/cc-auto-orchestrate/tree/main/claude-code/skills/codebase-stats
Command: npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill codebase-stats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Codebase health insights are hard to obtain from scattered data; this Skill collects metrics and debt indicators to provide a cohesive view of codebase health.

Core Features & Use Cases

  • Collects base metrics (LOC, functions, classes) across languages and projects.
  • Identifies hotspots and debt indicators (TODO/FIXME/HACK) for prioritization.
  • Compares metric snapshots over time to reveal trends and guide refactoring decisions.
  • Use cases include baseline audits, incremental health tracking, and debt reduction prioritization.

Quick Start

Run the codebase-stats skill against your repository to generate an initial metrics snapshot.

Frequently Asked Questions about codebase-stats

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure codebase health and track technical debt trends?▼

You can measure codebase health by collecting metrics like LOC, function counts, and debt indicators to quantify health. This Skill compares metric snapshots over time to reveal trends and guide refactoring decisions.

What is the best way to identify technical debt hotspots across multiple programming languages?▼

Identify technical debt hotspots by scanning for TODO, FIXME, and HACK markers across multi-language codebases. This process pinpoints problematic areas to help prioritize debt reduction and refactoring efforts effectively.

How do I generate a code quality report for a baseline audit of a large codebase?▼

Generate a code quality report by running the codebase analysis against your repository to create an initial metrics snapshot. This baseline audit captures base metrics and debt indicators to establish a health reference point.

Can I use codebase metrics to track incremental code quality improvements over time?▼

Yes, you can track incremental code quality improvements by comparing metric snapshots over time. This trend analysis reveals whether codebase health is improving or deteriorating to guide ongoing maintenance.

Does this codebase analysis approach work for medium to large multi-language projects?▼

Yes, this codebase analysis is designed to be applied to medium to large codebases across multiple languages. It collects base metrics and debt indicators regardless of the specific programming languages used.

What specific codebase metrics should I collect to prioritize technical debt reduction?▼

To prioritize technical debt reduction, collect base metrics such as lines of code, function counts, and class counts, alongside debt indicators including TODO, FIXME, and HACK comments to identify refactoring hotspots.