I built a tool that roasts your code with regex — no AI involved

Developer Adam Yasingh built Roast My Code, a client-side tool that scores code snippets for 'AI debt' using 118 regex patterns across eight languages, with no AI or backend involved. The tool generates an AI Debt Score and provides brutal one-liner roasts and fixes, aiming to help developers quickly assess code quality before opening pull requests.

The problem In 2026, devs spend 11.4 hours a week reviewing AI-generated code — more time than they spend writing it. We're burning cycles fixing bugs our own AI tools wrote. I started calling this "AI debt": the maintainability tax that piles up when nobody's actually reading the code the assistant just spat out. I wanted a fast, brutal way to see how much debt was hiding in a file before I even opened a PR. What I built Roast My Code — paste a code snippet, get an AI Debt Score 0–100 and get roasted for your sins. 118 regex patterns across 8 languages JS/TS, Python, Go, Rust, Java, PHP, C++ Scores broken into Readability, Structure, Error Handling, Safety, and Style Code metrics: nesting depth, duplication %, comment ratio, avg line length Three brutal one-liner roasts + concrete fixes for each issue found The twist: zero AI. No API calls, no LLM, no backend. Everything runs client-side with regex pattern matching. Your code never leaves your browser. Why regex, not AI Honestly — irony. A tool built to call out AI slop shouldn't itself be another wrapper around GPT. Regex is also just... faster. No API latency, no cost, no rate limits, no "please wait while I analyze your code" spinner. You paste, you get roasted in under a second. It's not going to catch everything a proper linter or an LLM code reviewer would. That's not the point — it's a gut-check, not a static analysis suite. A taste of the roasts javascript var API KEY = "sk live 51H8xJ2kL9mNpQrStUvWxYz..."; if a == 1 { if b == 2 { if c == 3 { x = eval a + b + c ; } } } 🔒 is that a hardcoded credential? in 2026? we need to talk. your teammate rewrote this on a Sunday. FIX: Move it to an environment variable or secret store, then rotate the credential. 🎆 eval . we don't need to say more. you know what you did. this is the part reviewers skim past. FIX: Replace eval with a lookup table, JSON.parse, or an explicit parser. Try it 🔗 Live app 💻 Source on GitHub — MIT licensed, PRs welcome Paste your worst code and see what it says. Screenshot the damage, share it, pretend you're not crying. Would love feedback — especially on rules that are missing, or ones that fire when they shouldn't. GitHub: https://github.com/adamyasingh-05/roast-my-code https://github.com/adamyasingh-05/roast-my-code Live app Lovable : https://easy-link-free.lovable.app https://easy-link-free.lovable.app