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

Troubleshoot non-responsive Bash systems

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 'web_server_01' system is unresponsive. I need you to check its running processes, review…+
The 'web_server_01' system is unresponsive. I need you to check its running processes, review the last 100 lines of the system log, and attempt to restart the Apache service. If it's still down, gather disk usage and memory statistics.
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 declare 'web_server_01' dead, make sure we've explored all angles. Check for high CPU…+
Before I declare 'web_server_01' dead, make sure we've explored all angles. Check for high CPU usage by any single process, look for recent kernel panics in the logs, and verify network connectivity to its default gateway, so we don't miss an obvious fix.
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 main database server, 'db_prod_01', just stopped responding to pings and SSH. The…+
A critical production server is unresponsive, and I'm getting conflicting information.
The main database server, 'db_prod_01', just stopped responding to pings and SSH. The monitoring system says it's down, but the network team claims their side is fine. I'm afraid to force a hard reboot without understanding why it went down, risking data corruption, but every minute it's down costs us thousands. I don't know if it's a kernel issue, a disk failure, or just a hung process. What's the safest first step to diagnose the actual problem without making it worse or losing critical uptime?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently waste critical time and make hasty decisions when a production system goes…+
I always panic and waste time when a critical system becomes unresponsive.
I consistently waste critical time and make hasty decisions when a production system goes unresponsive, often leading to longer downtimes or unnecessary reboots. I'm afraid of missing the root cause under pressure. What habit should I change to approach troubleshooting non-responsive systems more systematically and calmly, so I can diagnose and resolve issues faster and with less stress?
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.