Debug My Failing Test

You know you should. Paste the function — get the test cases that actually catch bugs, including the edge cases you'd forget at 6pm.

Stuck? Explain the problem to it out loud. It asks the questions that make you find your own bug — and only steps in when you're truly stuck.

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

"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.

The thing every dev skips. Tell it what your project does — get a README people can actually follow: what it is, how to run it, and why it exists.

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.

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.

Got the logic in plain steps but not the syntax? Write it out however you think — get clean, working code in your language, with the logic preserved.

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.

Porting code to a new language or framework? Paste it — get the converted version plus the traps that don't translate one-to-one.

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.

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.

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.

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.

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.

Designing an API and want it to not be a regret in six months? Describe what it does — get clean endpoints, naming, and the edge cases you'd forget.

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.

Stop guessing. Give it the symptom and the code — it ranks the likely causes and tells you the one thing to test next. Diagnoses before it touches a fix.

Paste your code. It reviews like it's shipping to a million users tomorrow — bugs, security holes, the slow stuff — ranks every issue, and ends with ship or don't. No flattery.

Stop deploying by hand and praying. Tell it your stack and host — get a CI/CD setup that tests and ships automatically, with the config and the why.

Building against an API that isn't ready? Describe the endpoint — get realistic mock JSON (success and error cases) so you can build the front end now.

That boring task you do by hand every week. Describe it — get a script to automate it, with setup steps simple enough that a non-coder can run it.

Practice coding interviews the right way. Paste the problem — it nudges you toward the solution with hints, only revealing the answer once you've actually tried.