Write My README

Describe what you want to match in plain words. Get the regex, every piece explained, and test cases — so you actually trust it before you ship it.

"Works on my machine" — famous last words. Describe your app — get a Dockerfile and setup that runs the same everywhere, explained so you understand it.

It works but it's slow. Paste it — get where the real bottleneck is, the optimized version, and whether the speed-up is even worth the complexity.

Paste the stack trace that means nothing to you. Get what actually broke, why, and the most likely fix — in plain English.

Find the holes before someone else does. Paste your code — it runs an OWASP-style security review and tells you what an attacker would try first.

"fixed stuff" is not a commit message. Paste your diff or describe the change — get a clear commit message your future team will actually thank you for.

Don't pick a stack you'll fight for years. Describe what you're building and your skills — get a real recommendation with trade-offs, not hype.

Naming things is half of programming and you're stuck. Paste the code or describe it — get clear, consistent names that make the code read itself.

Dropped into unfamiliar code? Paste it. Get the map — what it does, how it flows, and where the bodies are buried — before you touch a thing.

Paste the function you're embarrassed by. Get it cleaner and readable with the exact same behavior — plus a note on what was wrong so you stop doing it.

Got dropped into a framework you've never used? Name it and what you know — get the mental model, the core concepts, and the 20% you need to be productive today.

A config file full of settings you're scared to touch. Paste it — get what each part does, which knobs are safe to change, and which will break things.