Viktor.comAn AI coworker that actually does the work
Promoted
ReadmeRoast
Your README gets roasted. Your repo gets better.
6 followers
Your README gets roasted. Your repo gets better.
6 followers
Paste a public GitHub repo. Claude roasts your README like a comedy-club guest of honor: a Burn Rating out of 100, a set list of brutal-but-useful critiques, and a fully rewritten README you can copy and ship tonight. Free, no signup.
Hey Product Hunt! 👋
I built ReadmeRoast in a weekend after a humbling realization: I'd spent months building projects, and my READMEs were quietly sabotaging all of them. The repo IS the landing page — and mine read like commit messages with ambition.
So I built the reviewer I needed: paste any public GitHub repo, and it delivers a comedy-club roast — a Burn Rating out of 100, a "set list" of critiques, and the part that actually matters: a complete rewritten README you can copy and ship immediately. Every burn comes with a fix.
First thing I did was point it at my own security project. It scored 62/100 and called it "a TED talk that forgot to mention where you buy tickets." It flagged my missing license and absent install instructions. It was right. I fixed both. That's the whole loop: roast → fix → ship.
Under the hood it's deliberately boring: a single-page Next.js app, one serverless route, Claude via Vercel's AI Gateway, no database, no signup, MIT-licensed on GitHub.
My ask: roast your own repo and tell me the harshest line it gave you — best burn in the comments gets a place of honor and if it breaks on some cursed README format, tell me; I'll be fixing things live all day.
🔥 https://readme-roast.vercel.app
Does the roast stay the same if I rerun it later, or does it generate a fresh burn each time you hit the button?
@ykselhzrer9n0b Fresh burn every time 🔥 Nothing's cached in v1 — every roast is a live take, so the comedian improvises new material on each run. The score usually lands in the same range (your README's actual problems don't change), but the jokes do. A few people have been re-rolling just to see the harshest possible line — honestly the correct way to use it 😄
V2 is already in the works with permanent roast pages, so a saved roast becomes a proper before/after (62 → 84, receipts included).