language-analyzer

Identify programming languages and code metrics from a repository JSON report.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/0x53c7/security-testing-rovodev-skills --skill language-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: language-analyzer
Source: https://github.com/0x53c7/security-testing-rovodev-skills/tree/main/.rovodev/skills/language-analyzer
Command: npx skills add https://github.com/0x53c7/security-testing-rovodev-skills --skill language-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify the programming languages and code composition of a codebase to guide tooling decisions and rule selection during security reviews.

Core Features & Use Cases

  • Detect programming languages and file counts with a single run.
  • Produce a structured summary of languages, file counts, and lines of code to inform stack decisions.
  • Use during kickoff to size the scope of review and select appropriate rulesets.

Quick Start

Run the language-analyzer on the target repository to obtain a JSON summary of languages and code metrics.

Frequently Asked Questions about language-analyzer

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

FAQPage Schema
How do I analyze programming languages and code metrics in a repository?

You analyze codebase languages and metrics by running a tool that identifies code composition and generates a structured JSON summary of file counts and lines of code.

What is the best way to identify code language distribution for a security review kickoff?

The best way to identify code language distribution for a security review kickoff is to generate a fast structured summary of languages and lines of code to inform stack decisions and ruleset selection.

Do I need cloc to generate a JSON report of codebase metrics?

Yes, you need cloc installed because the analysis requires cloc to generate the JSON report containing language distribution and code metrics for the target repository.

Can I exclude specific directories when analyzing code composition?

Yes, you can exclude specific directories when analyzing code composition because the tool supports optional directory exclusions to refine the language and metrics report for your target repository.

What code metrics are included in the language analysis report?

The language analysis report includes code metrics such as identified programming languages, file counts, and lines of code, providing a structured summary to guide tooling decisions.