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

Fix Bash performance issues

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.

3prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun a profile on the 'database_query_optimizer.sh' script to identify the slowest functions.…+
Run a profile on the 'database_query_optimizer.sh' script to identify the slowest functions. Focus on calls to external utilities and large file operations. Output the top 10 most time-consuming sections to a file named 'optimizer_profile_report.txt' in the current 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 the 'data_ingestion_pipeline.sh' script to production, help me optimize its…+
Before I push the 'data_ingestion_pipeline.sh' script to production, help me optimize its execution time. Look for inefficient loops, redundant commands, and opportunities to parallelize tasks. Suggest specific changes to improve performance without altering the core logic.
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 'nightly_etl.sh' script stalled for the third time this week, specifically after the…+
The nightly data processing script just hung again, right after a large data transfer.
The 'nightly_etl.sh' script stalled for the third time this week, specifically after the 'rsync' command for the 200GB data dump. The log just stops. I'm afraid of missing the morning report deadline, and I can't keep restarting it manually. What's the most likely cause of the hang, and what's the quickest way to diagnose and get it running stably for tonight?
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.