vibe-coding

Type English. Ship code. Track the ratio.

The Problem

You tell Claude what to build. Claude writes the code. But nobody's measuring the ratio. How many words did you type to ship 2,847 lines? What's your personal multiplier? Is it going up?

Stop counting lines of code written. Start counting lines of English typed. That's the real metric now.

Quick Start

# Start a tracked vibe coding session
npx vibe-coding start

# Check your stats
npx vibe-coding stats

# Generate a badge for your README
npx vibe-coding badge

No API key needed — wraps Claude Code and reads git diffs locally.

Example Output

Session End

  ╭───────────────────────────────────────╮
  │         VIBE CODING STATS             │
  ├───────────────────────────────────────┤
  │  Latest Session  2026-02-27           │
  │  Words typed:        43               │
  │  Lines generated:    2,847            │
  │  Ratio:              66:1 🔥          │
  │  Duration:           47m              │
  │  Files changed:      12               │
  ├───────────────────────────────────────┤
  │  All Time                             │
  │  Total sessions:     23               │
  │  Total words:        891              │
  │  Total lines:        47,293           │
  │  Lifetime ratio:     53:1             │
  │  Time saved:         ~1,182 hours     │
  ╰───────────────────────────────────────╯

Badge Mode

$ npx vibe-coding badge

  Badge written to vibe-badge.svg
  Add to your README:

  ![Vibe Ratio](vibe-badge.svg)

Features

• Wraps Claude Code and tracks every English instruction you type
• Counts lines generated via git diff --stat after each change
• Calculates your personal typing-to-code multiplier
• Session history saved to ~/.vibe-coding/sessions.json
• Generates a shareable SVG badge for your README
• Estimates time saved vs manual coding (baseline: 40 lines/hour)
• All Time stats across every session

How It Works

1. npx vibe-coding start launches Claude Code inside a tracked wrapper
2. Every line you type is counted as "words typed"
3. After each Claude Code change, git diff --stat is read for lines generated
4. At session end, ratio is calculated and saved to local history
5. stats and badge commands pull from that history

What Counts

• Words typed: Your English instructions to Claude (not code you type manually)
• Lines generated: Actual code changes tracked via git diff
• Time saved: Estimated vs manual coding at ~40 lines/hour baseline

Ratio Scale

Ratio	Rating
50:1+	Green — peak vibe
20:1–49:1	Yellow — solid session
<20:1	White — keep vibing

Requirements

• Claude Code installed (claude in PATH)
• Git repo in your project directory (for diff tracking)
• Node.js 18+

See Also

• 100x-dev — Full velocity dashboard for AI-assisted development
• dev-journal — Auto daily dev journal from your git history
• pr-poet — PR descriptions that are actually good. Also: haikus.

License

MIT — NickCirv