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

Loop through file content

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 taskI need to go through every line in 'server-list.txt', which contains one server IP per line.…+
I need to go through every line in 'server-list.txt', which contains one server IP per line. For each IP, I'll run a 'ping -c 1' command and then log the result into 'ping-results.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 acceptBefore I run this nightly server health check, I want to make sure it's resilient. The…+
Before I run this nightly server health check, I want to make sure it's resilient. The 'server-list.txt' sometimes has blank lines or comments starting with '#'. How can I make sure my script only attempts to ping valid IP addresses and skips anything else, so I don't get errors or misleading results in 'ping-results.log'?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy script just crashed trying to ping an empty string from the server list. I'm looping through…+
My script just crashed trying to ping an empty string from the server list.
My script just crashed trying to ping an empty string from the server list. I'm looping through a file line by line, but some lines are empty or just comments. I'm afraid this will cause issues when the list changes. What's the best way to iterate through 'server-list.txt', processing only valid server IPs and ignoring blank lines or comments, without breaking the loop?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently write scripts that need to process configuration files line by line, but these…+
I frequently write scripts that need to process configuration files line by line, but these files are often messy.
I frequently write scripts that need to process configuration files line by line, but these files are often messy with comments, blank lines, or irrelevant data. I waste time debugging loops that choke on bad input. What habit should I change to make my file processing loops more robust and less prone to errors from malformed input files?
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.