Coding & developmentCommand-line toolscode
Check that dry-run matches real planned actions
Ensures preview cannot hide dangerous differences.

Ready to use
Prompt
Inputs: [CLI CODE], [ACTION TYPES], [TEST FIXTURES]. Trace dry-run and execute paths to a shared planner. Identify side effects that occur before confirmation and design fixture tests. Output: A side-effect inventory and dry-run parity tests. Check: Test whether dry-run lists every action execute would attempt from the same input snapshot; mark unrun tests as proposed, not proof of parity. If essential information is missing, identify it rather than filling the gap with a guess.