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

Handle complex dated and timed tasks

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 Bash tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSchedule the `cleanup_logs.sh` script to run every Sunday at 2 AM, and `rotate_db_backups.sh`…+
Schedule the `cleanup_logs.sh` script to run every Sunday at 2 AM, and `rotate_db_backups.sh` every first day of the month at 3 AM. Make sure both output logs to `/var/log/cron_jobs.log`.
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 acceptReview my `deploy_app_v2.sh` script. I need it to be more robust for production. Specifically,…+
Review my `deploy_app_v2.sh` script. I need it to be more robust for production. Specifically, ensure it handles network drops during `scp`, verifies file integrity after transfer, and logs all steps with timestamps to a file in `/var/log/app_deploys/`.
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 `migrate_db_schema.sh` script just bombed on staging. It returned a 'permission denied'…+
The database migration script just failed on staging, and I'm not sure if it's the script logic or a permissions issue.
The `migrate_db_schema.sh` script just bombed on staging. It returned a 'permission denied' error, but I double-checked the service account permissions last week. The lead developer is pushing for a quick fix before the client demo tomorrow. I'm worried about breaking production if I just force it. What's the most likely cause, and how should I safely diagnose this without further disrupting staging?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm tired of my scripts working perfectly in my dev environment but failing in production due…+
I keep writing scripts that work fine on my machine but break in production due to environmental differences.
I'm tired of my scripts working perfectly in my dev environment but failing in production due to missing dependencies or different paths. I waste so much time chasing down these inconsistencies. What's one habit I can change to ensure my scripts are more portable and robust across different environments, without having to manually check every single variable?
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.