code-info

Generates read-only Markdown metrics reports for local folders or GitHub repositories.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill code-info-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-info
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/code-info
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill code-info-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Manually gathering project statistics like lines of code, dependency counts, CLI command hierarchies, and coverage figures is repetitive and error-prone. This Skill produces a consistent, copy/paste-ready Markdown report from a local project folder or a GitHub repository without modifying any files. ## Core Features & Use Cases - Comprehensive Metrics: Reports project description, documented features, code/test/documentation LOC per language, per-component LOC, test file counts, and repo size. - CLI and Dependency Analysis: Statically detects CLI command hierarchies (Click, Typer, argparse, Commander, Cobra, clap) and counts direct, optional, and transitive dependencies from Python, Node.js, Go, and Rust manifests and lockfiles. - Remote GitHub Mode: Analyzes a repository without cloning by downloading a tar archive into a temporary directory, with token-based authentication for private repos. - Use Case: Before writing project documentation or a status update, run the report to get an accurate snapshot of codebase size, dependency footprint, and coverage, including approximate size comparisons against pinned Redis and SQLite source trees. ## Quick Start Ask the assistant to run the code-info report on the current project folder or on a named GitHub repository and return the Markdown metrics report.

Frequently Asked Questions about code-info

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

FAQPage Schema
How do I generate a code metrics report for a GitHub repository without cloning it?

Run the bundled script with --github-repo OWNER/REPO, optionally adding --github-ref for a branch, tag, or commit. It downloads a tar archive into a temporary directory, analyzes it, and deletes the directory after the report.

How to count lines of code per language in a project?

The script walks the project tree, classifies files by extension into languages, and counts non-blank, non-comment lines. It reports comparable code LOC, test LOC, documentation/configuration LOC, and per-language totals.

Does the analysis modify my project or run tests?

No. The skill is strictly read-only: it never edits, builds, installs, formats, or runs tests. It only reads files and runs read-only Git commands with GIT_OPTIONAL_LOCKS=0 to avoid touching the Git index.

Can I analyze a private GitHub repository?

Yes. Set GH_TOKEN or GITHUB_TOKEN, or authenticate the GitHub CLI so gh auth token works. The token is sent only in the request header and is never printed or stored.

Which dependency formats are supported for dependency counting?

It parses pyproject.toml, setup.cfg, requirements files, package.json, Cargo.toml, and go.mod, plus lockfiles like package-lock.json, Cargo.lock, poetry.lock, and Pipfile.lock for resolved and transitive counts.

Why are some metrics reported as unavailable?

Metrics that cannot be derived from existing files stay unavailable rather than being fabricated. For example, coverage appears only when a coverage artifact already exists, and resolved dependency counts are partial without a lockfile.