dry-run

You can preview command effects by running the command with the --dry-run flag, which simulates file writes, git operations, and state changes while skipping actual execution and logging agent spawns.

Command dry-run simulation is used for safe testing and debugging, allowing you to detect the --dry-run flag in arguments and output a standardized summary of simulated side effects without altering the actual system.

To test git operations safely, use the --dry-run flag to simulate commits and state changes, ensuring you can preview the exact modifications before pushing code to a branch.

Yes, you can track agent spawns during safe testing by running your command with the --dry-run flag, which logs agent spawns and monitors state changes without triggering actual write operations.

Yes, the --dry-run flag works for debugging unintended file modifications by detecting the flag in command arguments, skipping real execution, and generating a summary of simulated file writes for review.

The limitation of simulating side effects for safe testing is that it only previews and logs state changes without executing write operations, meaning actual system dependencies or runtime errors may remain undetected until real execution.