This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
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.
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.
Does the roast stay the same if I rerun it later, or does it generate a fresh burn each time you hit the button?
About ReadmeRoast on Product Hunt
“Your README gets roasted. Your repo gets better.”
ReadmeRoast was submitted on Product Hunt and earned 4 upvotes and 3 comments, placing #160 on the daily leaderboard. 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.
ReadmeRoast was featured in Developer Tools (515.5k followers), Artificial Intelligence (473.1k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 204.8k products, making this a competitive space to launch in.
Who hunted ReadmeRoast?
ReadmeRoast was hunted by Karthikeyan s. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how ReadmeRoast stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Karthikeyan s
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