$ ls -la drwxr-xr-x docs/ $ run script
◆ Bash

Control jobs in Bash

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 taskI need to stop the 'data_ingest_pipeline' job that's currently running on the development…+
I need to stop the 'data_ingest_pipeline' job that's currently running on the development server, but let the 'report_generator' job finish first. Then, restart 'data_ingest_pipeline' with the new configuration file from the '/tmp/configs/' directory.
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 new data processing job to production, help me set up a robust way to…+
Before I push this new data processing job to production, help me set up a robust way to monitor its memory usage and CPU load every 30 seconds. If either exceeds 80% for more than 5 minutes, I need an alert logged to '/var/log/system_alerts.log' and the job gracefully restarted.
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 'database_backup' job just hung again, right after the 'etl_process' finished, and I'm…+
The 'database_backup' job just hung for the third time this week, right after the 'etl_process' completed.
The 'database_backup' job just hung again, right after the 'etl_process' finished, and I'm worried about data integrity. The logs aren't showing any obvious errors, but the database server is under heavy load during the ETL. I can't afford another failed backup before the weekend. Is the ETL process locking resources, or is the backup script itself faulty under stress? What's the fastest way to diagnose and get a clean backup before Friday?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time trying to figure out which server a critical background job is actually…+
I keep losing time tracking down which server a critical background job is actually running on.
I keep losing time trying to figure out which server a critical background job is actually running on when I need to check its status or logs. I'm tired of SSHing into multiple machines to find it. What habit can I change to quickly identify the host for any given long-running process across our cluster?
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 Bash'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.