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

Perform audit and compliance 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 taskGenerate a report of all system changes made to production servers in the last 90 days by…+
Generate a report of all system changes made to production servers in the last 90 days by anyone in the 'Developers' group, showing the user, command, and timestamp. Put it in a CSV file named 'prod_changes_q3.csv' for the audit team by end of day.
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 hand this audit log to the compliance officer, make sure it's easy to read and verify.…+
Before I hand this audit log to the compliance officer, make sure it's easy to read and verify. Highlight any commands executed with root privileges, flag any changes outside of business hours, and add a summary count of changes per user so they can quickly spot anomalies.
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 external auditor just asked for all failed login attempts from external IPs over the past…+
The external auditor just asked for a specific log I can't immediately locate.
The external auditor just asked for all failed login attempts from external IPs over the past six months, specifically for the 'admin' user. I've checked the standard auth logs, but they only go back 30 days. I know we have archived logs, but finding the right compressed files and extracting that specific pattern across multiple servers feels overwhelming and time-consuming. I'm afraid of missing something critical or providing incomplete data. How can I efficiently search all archived logs across all servers for this specific pattern without crashing the system or taking days?
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 hours and credibility during audits because I can't quickly pull specific…+
I consistently struggle to quickly retrieve specific historical data for audits.
I keep losing hours and credibility during audits because I can't quickly pull specific historical log data across distributed systems. It's always a mad scramble to unarchive and grep files. What habit should I change to make audit data retrieval a routine, efficient process, so I'm always prepared and don't look incompetent?
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.