Paste your variables, functions, or files; get clearer names and the naming principles that make code self-explaining.
claudechatgptbeginner
The prompt
Help me name things in my code better.
The names I'm unsure about (with a line on what each does):
{{paste variables / functions / files}}
Language & conventions: {{context}}
Do this: 1) RENAME each — clearer, following my language's conventions (camelCase/snake, etc.), revealing intent not implementation. 2) THE WHY for each change in a few words. 3) THE SMELLS — names that hint at a deeper problem (a function named with 'and' is doing two things; a boolean named badly inverts logic). 4) THE PRINCIPLE — the one naming rule I'm breaking most, so I fix it everywhere. Good names remove the need for comments.
651 copies
Why this works
Names are read far more than they're written; a name that reveals intent ('unpaidInvoices' not 'data2') removes cognitive load on every future read — and a function name with 'and' in it is often two functions wearing a trenchcoat.
Shared by Sam Kowalski — Full-stack dev. Debugs out loud so you don't have to.
You are a senior engineer doing a patient code review.
Here's my error:
{{paste the full error message}}
Here's the relevant code:
{{paste the smallest chunk that reproduces it}}
Respond in exactly this order:
1. ROOT CAUSE — one sentence, no hedging.
2. THE MINIMAL FIX — smallest possible diff, shown as before/after.
3. THE MISCONCEPTION — what I likely misunderstood for this bug to exist, explained like I'm smart but new to this corner of the language.
4. THE SMELL TEST — one thing to check elsewhere in my codebase where I've probably made the same mistake.
Do not refactor unrelated code. Do not add features.
You are the most thorough reviewer on my team — kind, but nothing gets past you.
Here's my diff:
{{paste your diff or changed files}}
Context: {{what this change is supposed to do}}
Review it:
1. CORRECTNESS — bugs, edge cases, race conditions. Rank by severity; say "solid" if it's solid.
2. NAMING & CLARITY — the 3 spots a stranger would misread first.
3. THE QUESTION — what will a reviewer inevitably ask about this diff? Draft my answer.
4. TESTS — the one test that's missing and would catch a real regression.
Skip style nitpicks a linter would catch.
I'm stuck in git. Help me fix it without losing work.
What happened / what I want: {{describe — wrong branch, bad commit, need to undo, merge conflict, detached head...}}
Output of git status (and git log if relevant):
{{paste}}
Give me: 1) WHAT STATE I'm actually in, plainly. 2) THE SAFE FIX — exact commands in order, with what each does and why. Prefer non-destructive options; clearly flag anything that discards work before I run it. 3) HOW TO VERIFY it worked. 4) THE HABIT that prevents this next time. Assume I'll paste your commands literally — don't hand-wave.