◆ JavaScript

Clean up and maintain data

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a script to remove all duplicate entries in the 'customer_feedback' table where the…+
Write a script to remove all duplicate entries in the 'customer_feedback' table where the 'email' and 'comment_text' fields are identical, keeping only the oldest entry. Run it against the production database on Tuesday morning.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I run this data cleanup script on the customer feedback table, add a dry-run mode so I…+
Before I run this data cleanup script on the customer feedback table, add a dry-run mode so I can see what it will delete without actually committing changes. Also, include logging for each deleted record, and make sure it handles potential database locks gracefully.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm about to run a script to purge old user data, but the legal team just sent a vague email…+
I'm about to run a script to purge old user data, but the legal team just sent a vague email about new data retention policies.
I'm about to run a script to purge old user data, but the legal team just sent a vague email about new data retention policies. The project manager is pushing for the purge to meet compliance, but I'm afraid of accidentally deleting data that might now be required. I can't get a clear answer from legal before Friday. What's the best next move to avoid a compliance issue without blocking the PM?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself needing to clean up inconsistent or malformed data that should have…+
I frequently find myself needing to clean up inconsistent or malformed data that should have been caught earlier.
I frequently find myself needing to clean up inconsistent or malformed data that should have been caught earlier. This reactive cleaning takes up valuable time and introduces risk. What habit should I change in my development process to prevent data integrity issues from accumulating in the first place?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from JavaScript's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.