dry-run

Simulate command effects by detecting --dry-run flags and intercepting writes.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill dry-run-dyai2025
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dry-run
Source: https://github.com/DYAI2025/MOD_shark-engine/tree/main/sharkengine/.claude/skills/dry-run
Command: npx skills add https://github.com/DYAI2025/MOD_shark-engine --skill dry-run-dyai2025

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preview command effects without making changes by simulating reads, writes, and state mutations. This allows safe exploration of complex workflows before any real execution.

Core Features & Use Cases

  • Dry-run mode detection: Recognizes a --dry-run flag and prevents side effects.
  • Deterministic previews: Reports created/modified files, expected git operations, and state transitions.
  • Safe agent handling: Logs intended Task() spawns without executing them.

Quick Start

Run a command with --dry-run to see a complete preview of what would happen.

Frequently Asked Questions about dry-run

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preview command effects without executing state mutations?

You can preview command effects by simulating reads, writes, and state mutations using a dry-run mode. This intercepts write operations and provides a deterministic summary of intended actions, ensuring no actual changes occur.

How do I simulate git operations before applying changes?

Simulate git operations by running your command with a --dry-run flag. This detects the flag, prevents side effects, and reports the exact expected git operations and file modifications for your review.

Can I safely preview agent spawns and Task() executions?

Yes, you can safely preview agent spawns by logging intended Task() executions without actually running them. This safe agent handling logs the spawns so you can review the complete workflow safely.

What is the best way to test complex workflows without side effects?

The best way to test complex workflows without side effects is using a deterministic simulation. It previews created or modified files and state transitions, allowing safe exploration before any real execution.

Does dry-run mode work with any command or just specific frameworks?

Dry-run mode applies to any command. It universally detects the --dry-run flag, intercepts writes, and provides a deterministic summary of intended actions across various file and state operations.