◆ JavaScript

Fix lint errors

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 taskThe CI build failed and the lint job lists 87 errors across utils/date.js and…+
The CI build failed and the lint job lists 87 errors across utils/date.js and components/Header.jsx. Fix the lint errors so the build passes by Friday; run the linting locally, correct only genuine style or syntax issues (no feature changes), and push a single commit with 'fix: lint errors' so QA can re-run the pipeline.
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 fixes for the lint failures, make the changes easy to review: surface the files…+
Before I push fixes for the lint failures, make the changes easy to review: surface the files changed and number of errors up front, group fixes by type (semicolons, unused vars, arrow-body style), and mark any locations where a deeper logic change might be tempting so a reviewer can ignore or approve style-only edits.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe CI lint stage failed on utils/date.js and components/Header.jsx. I am the only engineer on…+
CI lint stage failed and shows many errors.
The CI lint stage failed on utils/date.js and components/Header.jsx. I am the only engineer on the repo today, and I worry that fixing everything at once will hide functional changes. I cannot tell which errors are purely style and which might mask a bug. Which files or patterns should I fix first to unblock CI with minimal risk, and what quick checks catch accidental behavior changes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery sprint we waste time on last-minute lint fixes that break tests or hide refactors. I can…+
We always scramble to fix linter errors right before a release.
Every sprint we waste time on last-minute lint fixes that break tests or hide refactors. I can see common causes: no pre-commit hooks, inconsistent editor configs, and merges from feature branches with differing rules. Which habits should I change first to stop this recurring firefight and keep the linter green between releases?
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.