Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Write a script to [file operation] inside [explicit directory]. Define allowed patterns, recursion, exclusions, output locations, and overwrite behavior. Add a dry run that shows the same selected paths and validations as the real run. Use a small fixture with normal, malformed, empty, conflicting, and unrelated files. Verify the intended output and repeat-run behavior. Keep diagnostics separate from machine-readable output and return meaningful exit codes. Explain the command, working-directory assumptions, and recovery procedure before applying it to the real collection.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.
- Python — File copying and archive operations
- Ansible — Dry-run check mode and its limitations
- Python — Path resolution, globbing, and file operations
- Microsoft Learn — PowerShell ShouldProcess and WhatIf preview behavior
Documentation links checked .
Editorial review · October 28, 2026
Corrected: The Ansible check-mode link returned a 429/bot response in the separate availability audit. Add an accessible primary alternative that explains dry-run preview behavior while retaining the original relevant reference. This remains an original, unexecuted instructional example.