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

Manage Linux file permissions

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 taskChange the permissions on the /var/log/app_logs directory to allow group write access for the…+
Change the permissions on the /var/log/app_logs directory to allow group write access for the 'developers' group, and ensure new files created in it inherit this group. Make sure only the owner can execute files in this 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 acceptI need to set up a new project directory for the 'analytics' team under /srv/projects. Before I…+
I need to set up a new project directory for the 'analytics' team under /srv/projects. Before I finalize the permissions, help me think through the security implications. They need to create, read, and modify their own files, but other teams shouldn't be able to see their data. What's the tightest way to set this up so it's secure but still usable for them, and also easy to maintain if new team members join?
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 new 'inventory-api' service is crashing on startup with 'permission denied' when trying to…+
I'm trying to deploy a new web service, but it keeps failing with 'permission denied' errors when trying to write to its data directory, even though I thought I set it up correctly.
The new 'inventory-api' service is crashing on startup with 'permission denied' when trying to write to /opt/inventory-api/data. I've already tried `chmod 755` on the directory and `chown inventory-api:inventory-api` on the files, but it's still failing. I'm afraid I'll introduce a security vulnerability if I just open everything up, and I can't tell if it's the user, the group, or something else. What's the most likely cause here, and what's the safest next command to diagnose this without breaking anything?
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 constantly fixing permission errors for new deployments, usually because a service can't…+
I keep getting called in on weekends because a new script or service can't write to its log or data directory due to permission issues.
I'm constantly fixing permission errors for new deployments, usually because a service can't write to its designated directory. It feels like I'm always guessing at the right owner and group. I need a better habit for how I set up new application directories and their permissions from the start, so I'm not scrambling every time a new service goes live. What's a robust approach I should adopt?
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.