Stats
Actions
Tags
From my-first-plugin
Analyze a codebase directory and report statistics (file counts by type, line counts, largest files)
How this skill is triggered — by the user, by Claude, or both
Slash command
/my-first-plugin:code-statsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze the codebase at the path given by $ARGUMENTS (default: current working directory).
Analyze the codebase at the path given by $ARGUMENTS (default: current working directory).
Report the following statistics:
Use Glob to find files and Read to sample files when needed. Keep output concise and well-formatted as a markdown table where appropriate.
npx claudepluginhub haseebahmed-official/my-plugin-marketplace --plugin my-first-pluginCounts source lines by file type and auto-detected modules via shell inspection. Handles JS/TS monorepos, Rust/Go/Python workspaces, Java/Kotlin multi-module, full-stack monoliths.
Counts lines of code, analyzes codebase size/composition, and compares code between versions using `cloc`. Supports 200+ languages and multiple output formats.
Generates a compact project map listing every file's size, token estimate, and category. Highlights total token cost, heaviest files, and structure breakdown for quick codebase understanding.