◆ JavaScript

Run test suite

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
See the prompt↓All JavaScript tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe test suite on the CI failed on the feature branch; run the full tests locally, fix obvious…+
The test suite on the CI failed on the feature branch; run the full tests locally, fix obvious unit failures, and re-run until everything passes. Start with the failing test file test/auth.test.js and finish by running npm test to produce a clean green run on my machine by end of day.
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 push this branch to the shared pipeline, make it easy for reviewers to verify test…+
Before I push this branch to the shared pipeline, make it easy for reviewers to verify test coverage and recent failures -- surface the failing test names and stack traces up top, list any mocked network calls, and flag tests that take longer than 500ms. Also suggest which failures look flaky versus real.
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 ran the auth flow locally and one integration test failed after passing yesterday; the…+
A single integration test just started failing on my machine
I ran the auth flow locally and one integration test failed after passing yesterday; the failure happens in test/auth.integration.js when it times out at the login POST. I don't know whether a recent mock change, my local environment, or a genuine regression caused it. Which likely source should I check first and what concrete next step will isolate whether the timeout is environmental or code-related?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver the last three sprints I keep losing time debugging tests that fail only on my machine or…+
Tests intermittently fail on branches before merge
Over the last three sprints I keep losing time debugging tests that fail only on my machine or in CI windows; I waste hours reproducing flaky network mocks and slow fixtures. Where am I most likely creating fragility and what habit should I change to reduce these firefights going forward?
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.