Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Review [bulk command or script] before applying it to [named target directory]. Inspect the actual code and argument handling.
Explain which paths it resolves, what it reads or changes, and how it handles missing files, name collisions, links, and permission failures. Verify that the final resolved targets stay within the intended boundary. Check quoting or argument construction for spaces and shell-special characters.
Prepare a dry-run report and test the behavior on representative temporary data in the project workspace. Identify irreversible effects and the available recovery procedure. Report findings and a precise execution example; do not treat a successful dry run as proof that external state cannot change afterward.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Node.js — Cross-platform path operations
- Node.js — File system operations
- Microsoft — PowerShell ShouldProcess and WhatIf
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted command review. Microsoft's preview guidance and Node's path/file semantics support the checks; dry run cannot certify unchanged future external state.