OneLinersCommand workbench
AI
Back to prompts
plain-prompt

Review a PowerShell script

Inspect parameter binding, pipeline objects, error semantics, quoting, and compatibility.

Revision
1
Verified
2026-07-26
Save or explore
Save to collectionCreate a collection in the sidebar first.

Compatibility and paths

GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI

Trust and provenance

Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.

Fill variables

Values stay in this browser tab and are not stored.

Generated asset2 required field(s) must be completed
Objective: Find behavioral and compatibility defects with exact cmdlet semantics.

Context: PowerShell 7 is primary; mark Windows PowerShell 5.1 differences.

Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.

User request:
PowerShell/platform:
{{environment}}

Script:
{{evidence}}

Review with safe alternatives.

Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop condition

Real example

Input

Get-ChildItem $Path | ForEach-Object { Remove-Item $_.Name }

Expected result

Risk: `Name` is relative to the current location, not necessarily the enumerated directory. Pass `FullName`, add `-LiteralPath`, and expose `SupportsShouldProcess` for destructive behavior.

Source evidence

PowerShell documentationofficial