cleanvibes.ogbuilds.aicode cleanliness scores for vibe-coded apps
clean·vibes reads a github repo like a picky reviewer, hunting huge files, deep nesting, copy-pasted blocks, and dead code. then it hands back a 0-100 score and six weighted subscores. every finding comes with file, line, and a ready-to-paste claude prompt.
clean·vibes55.6%
of 549 vibe-coded repos had duplicated logic
60.5%
had files past the oversized-file thresholds
59.2%
contained commented-out code
cleanvibes rules-engine study · 549 public self-described AI/vibe-coded GitHub repos · july 2026 · read the full study →
clean·vibesbefore & after
an app that shipped faster than its cleanup
beforeno idea where the mess is: huge files, dead code, copy-paste
aftera 0-100 cleanliness score with six subscores, every spot located
knowing what to fix first
beforefindings buried, no severity, nothing actionable
afterevery finding ranked by severity with file and line
actually cleaning it up
beforerewrite messy code by hand, risk breaking behaviour
aftera ready-to-paste claude prompt with behaviour-preserving constraints
simple pricing
Free
see where your codebase stands
4 credits · one free haiku scan
- cleanliness reviews on claude haiku
Pro
whole-repo reads, watched weekly
300 credits / mo · 30 scans
everything in free, plus:
- claude opus scans: our deepest pass, every subscore checked
- weekly monitoring: re-scans + an email the moment your score drops
- scans your private repos
- export findings as github issues + one-click fix prs
every plan includes
- 0-100 score + six subscores
- every finding with file + line
- ready-to-paste claude fix prompts
- readme badge + share links
a look inside
a few of the screens you'll actually use.
- 0-100 score + six subscores
- every finding, file + line
- ready-to-paste claude prompts
clean·vibeshow clean is your vibe-coded app?
paste a github repo — get a cleanliness score, ranked findings, and the claude prompts that tidy them.
clean·vibesclean·vibes guides
Ways to use clean·vibes, and how it compares.
- use caseYour codebase's cleanliness score, explained: the exact math behind clean·vibes's 0–100Code cleanliness score, explained: clean·vibes grades repos 0–100 from six weighted categories. The exact math, weights, and grade bands, no black box.
- how toHow to clean up vibe-coded apps: the tidy-up pass AI-built repos never getClean up AI-generated code in order: giant files, pasted blocks, commented-out leftovers, warring styles. The cleanup pass, and how clean·vibes runs it.
- how toHow to detect and delete dead code (commented-out blocks, TODO piles, debug leftovers)Dead code detection: find commented-out blocks, stale TODOs, and leftover console.logs in any repo, by hand or in one paste with clean·vibes.
- use caseHow much code duplication is too much — and which copies actually matterCode duplication: how much is too much? A practical line between harmless copies and bugs you fix four times, and how clean·vibes detects and scores it.
- use caseConsistency in a codebase: filenames, indentation, and the phantom diffs they causeNaming consistency: mixed tabs, three filename conventions, two package managers add up to phantom diffs. What consistency buys, how clean·vibes scores it.
- how toRepo hygiene checklist: README, .gitignore, lockfile, and the junk that shouldn't be in gitRepo hygiene checklist: node_modules committed, no README, no lockfile, zero tests. The easiest fixes, in order, checked by clean·vibes in one paste.