Code review & debugging21 categories
Two fixes, pick one
Two plausible approaches and no strong feeling about either.
I have two ways to fix this. Compare them on correctness, on what each one makes harder later, and on how obvious each is to the next person reading it. Then pick one and commit to it. I do not want a balanced summary. Option A: Option B:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Refactoring and design calls. Cutting code down, naming things properly, and choosing between two workable options.
Related prompts
Delete as much of this as possibleCode that works but feels bigger than the problem.Better names for these thingsWhen you've written `data2`, `handleThing`, or `utils`.Improve these error messagesErrors that say "something went wrong".Critique this API designBefore other people start depending on an interface you're designing.Should I add this dependency?Before `npm install` on something you could write yourself.Name this functionYou've called it doThing and you know it.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free