Check an admin script or command before running it
Explains what an unfamiliar script or command will actually do, flags risky lines, and suggests a safer way to run it.
The prompt
Explain this script or command before I run it, and flag anything risky.
Script or command: [PASTE]
Where I got it: [vendor docs / forum / colleague / AI-generated / unknown]
Where I plan to run it: [e.g. "domain controller", "100 laptops via Intune", "production Linux server"]
Permissions it will run with: [admin / root / standard user / service account]
What I want it to do: [MY GOAL]
Review:
1. Plain-language walkthrough: what each section does, in order.
2. Does it do what I want? Note any gap between my goal and the actual behavior.
3. Risky actions: deletions, recursive changes, registry or system file edits, disabling security tools, network downloads, encoded or obfuscated content, credential handling, outbound connections, persistence (scheduled tasks, services).
4. Hidden assumptions: hard-coded paths, OS versions, missing error handling, behavior if a variable is empty.
5. Red flags that suggest malicious intent, explained without guessing.
Then suggest:
- A safer version: dry-run or what-if mode, logging, confirmation prompts, scoping to a test group first.
- How to test it: on one non-critical machine or a snapshot, and what to check after.
- A rollback approach.
Return: a risk rating (low/medium/high), the walkthrough, a table of risky lines (Line | What it does | Risk | Fix), and the safer version with comments. If something is ambiguous, say so rather than assume it is safe.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- PASTE
- vendor docs / forum / colleague / AI-generated / unknown
- admin / root / standard user / service account
- MY GOAL
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Audit a codebase for bugs, risks, and tech debtA systematic review of a repository with prioritized findings and a remediation plan.
- Learn a programming language or conceptA patient coding tutor that explains concepts, gives exercises, and reviews your solutions.
- Refresh an old article to rank againUpdates an existing article for current intent, accuracy, and depth.
- Create a test plan and test casesA risk-based test strategy with test cases for functional, integration, and end-to-end testing.