Write Better Commit Messages

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.

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

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.

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.

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.

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

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.

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.

Test's red and you don't know if it's the code or the test. Paste both — get whether the test is wrong, the code is wrong, and exactly what to fix.

Stuck on what to charge? It walks you through value, costs, and what the market bears — then gives you a number with the reasoning, not a vibe.

Lawyers cost money by the minute — walk in prepared. Describe your situation — get the right questions to ask, what to bring, and how to not waste the consult.

Brainstorm wide, then get brutal. Give it your challenge — it throws 20 ideas (including weird ones), then cuts to the 3 actually worth your time.