cleanvibes
code cleanliness scores for vibe-coded apps
cleanvibes is the tidy-up pass your vibe-coded app never got. Paste a GitHub link and it reads the repo like a picky reviewer — hunting huge files, deep nesting, copy-pasted blocks, dead code, and committed junk — then hands back a 0–100 score, a grade, and six weighted subscores so you know exactly where the mess lives.
Every finding comes with the file and line, why it matters, and a ready-to-paste Claude Code prompt with behaviour-preserving constraints — so the same kind of tool that wrote the mess can clean it up.
how it works
- 01
paste your repo link
Drop in any GitHub URL — the archive is streamed in memory, nothing written to disk. Sign in with GitHub for private repos.
- 02
read your score
One number, six weighted subscores, and every finding ranked by severity with file + line.
- 03
paste the fix
Each finding ships a Claude-ready prompt with behaviour-preserving constraints. Paste it, review the diff, re-scan.
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
how clean is your vibe-coded app?
paste a github repo — get a cleanliness score, ranked findings, and the claude prompts that tidy them.
cleanvibes guides
Ways to use cleanvibes, and how it compares.
- use caseYour codebase's cleanliness score, explained: the exact math behind cleanvibes's 0–100cleanvibes scores a repo 0–100 with a letter grade, built from six weighted categories where findings deduct points by severity. Here's the exact math — weights, deductions, grade bands — so the number means something instead of being a black box.
- how toHow to clean up vibe-coded apps: the tidy-up pass AI-built repos never getApps built fast with Claude Code, Cursor, or Copilot tend to ship the same six kinds of mess — giant files, pasted blocks, commented-out leftovers, warring styles. Here's the ordered cleanup pass, and how cleanvibes runs it for you.
- how toHow to detect and delete dead code (commented-out blocks, TODO piles, debug leftovers)Dead code never breaks the build, so it never gets cleaned. Here's how to find commented-out blocks, stale TODOs, and leftover console.logs in any repo — by hand, and in one paste with cleanvibes.
- use caseHow much code duplication is too much — and which copies actually matterSome duplication is harmless; some means every bug fix has to land four times. Here's a practical line between the two, how duplication is detected, and how cleanvibes scores it.
- use caseConsistency in a codebase: filenames, indentation, and the phantom diffs they causeMixed tabs and spaces, three filename conventions, two package managers — each inconsistency is small, but together they produce phantom diffs and constant friction. What consistency actually buys, and how cleanvibes scores it.
- how toRepo hygiene checklist: README, .gitignore, lockfile, and the junk that shouldn't be in gitnode_modules committed, .DS_Store everywhere, no README, no lockfile, zero tests — repo hygiene is the easiest cleanliness category to fix completely. The checklist, in order, and how cleanvibes checks it in one paste.