code-metrics

Measure repository code size and test metrics from actual source files.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/fukukei23/claude-config --skill code-metrics-fukukei23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-metrics
Source: https://github.com/fukukei23/claude-config/tree/main/skills/code-metrics
Command: npx skills add https://github.com/fukukei23/claude-config --skill code-metrics-fukukei23

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openpyxl, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents inaccurate portfolio and engineering reports by measuring code size and test coverage from actual repository files instead of relying on estimates or assumptions.

Core Features & Use Cases

  • Repository Code Measurement: Calculates application and test code line counts across supported programming files while excluding generated artifacts, virtual environments, and irrelevant directories.
  • Validation Workflow: Provides multi-layer verification using file samples, byte-size consistency checks, and git history review to prove measurements were based on real repository contents.
  • Use Case: When preparing a technical resume or portfolio, use this Skill to verify claimed code volume and test metrics across multiple projects and record the results in a source-of-truth document.

Quick Start

Ask the AI to measure the code lines and test cases for my repositories and record the verified results in the SSOT.

Frequently Asked Questions about code-metrics

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

FAQPage Schema
How do I measure actual code lines and test cases in a repository for a portfolio audit?

You can verify code volume claims for a technical resume by applying multi-layer validation: scanning actual source files, performing byte-size consistency checks, and reviewing git history. This proves measurements match real repository contents, preventing inaccurate portfolio reporting.

How do I verify code volume claims for a technical resume using git history?

You can verify code volume claims for a technical resume by applying multi-layer validation: scanning actual source files, performing byte-size consistency checks, and reviewing git history. This proves measurements match real repository contents, preventing inaccurate portfolio reporting.

Does line counting exclude generated artifacts and virtual environments during repository analysis?

Line counting during repository analysis does exclude generated artifacts, virtual environments, and irrelevant directories. It applies deterministic file scanning rules to supported programming files to ensure only actual application and test code metrics are measured.

Can I export code metrics and test measurements to a spreadsheet for engineering reports?

You can export code metrics and test measurements to a spreadsheet for engineering reports using optional openpyxl support. This allows you to record verified codebase reporting results across multiple repositories into a source-of-truth document.

What's the best way to audit code size across multiple repositories without relying on estimates?

The best way to audit code size across multiple repositories without estimates is to use deterministic file scanning combined with validation samples and test counting methods. This approach produces trustworthy engineering metrics derived directly from actual source files.