Skip to content

Code Stats

Verified

Visualizes repository complexity by counting files, lines of code, and grouping by extension. Use to assess project size or growth.

1,212 downloads
$ Add to .claude/skills/

About This Skill

# Code Stats

Analyzes the current workspace to provide development metrics.

Usage

```bash node skills/code-stats/index.js [path] ```

Defaults to current working directory if path is omitted.

Output

  • JSON object with:
  • `files`: Total file count.
  • `lines`: Total line count (approximate).
  • `byExt`: Breakdown by file extension.

Use Cases

  • Generate development metrics for the current workspace including line counts and file stats
  • Analyze codebase size and composition by language and directory
  • Track codebase growth over time by running periodic stat snapshots
  • Compare project sizes across repositories for resource planning
  • Identify disproportionately large files or directories that may need refactoring

Pros & Cons

Pros

  • +Simple Node.js script that runs with a single command and no configuration
  • +Defaults to current working directory for zero-friction usage
  • +Provides quantitative metrics useful for planning and reporting

Cons

  • -Only counts basic metrics — no complexity analysis or quality scoring
  • -Only available on claude-code and openclaw platforms
  • -Node.js runtime required even for analyzing non-JavaScript projects

FAQ

What does Code Stats do?
Visualizes repository complexity by counting files, lines of code, and grouping by extension. Use to assess project size or growth.
What platforms support Code Stats?
Code Stats is available on Claude Code, OpenClaw.
What are the use cases for Code Stats?
Generate development metrics for the current workspace including line counts and file stats. Analyze codebase size and composition by language and directory. Track codebase growth over time by running periodic stat snapshots.

100+ free AI tools

Writing, PDF, image, and developer tools — all in your browser.

Next Step

Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.