dry-run

Simulate command side effects without executing them.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill dry-run-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dry-run
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/dry-run
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill dry-run-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables safe command testing by simulating all side effects without making real changes, allowing teams to validate workflows without risking production state.

Core Features & Use Cases

  • Read-safe analysis: Processes command contexts through reads to accurately predict outcomes.
  • Full dry-run simulation: Logs all writes, edits, and side effects without executing them.
  • Agent spawn visibility: Records Task() invocations to show planned agent activity without spawning.
  • State-change preview: Projects YAML/state mutations and Git operations to guide real runs.

Quick Start

To preview a command's effects, run it with --dry-run, e.g.: /implement --dry-run The tool will emit a structured, emoji-prefixed summary showing what would occur and how to run the command for real.

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 side effects without modifying files or state?

Dry-run simulation previews command side effects by logging writes, edits, and state mutations without executing them. It processes command contexts through safe reads to accurately predict outcomes and emits a structured summary to guide real runs.

Can I test agent spawns and Git operations safely before running a command?

Yes, testing agent spawns and Git operations safely is possible by recording Task() invocations and projecting state mutations without actual execution. This visibility shows planned agent activity and Git changes to validate workflows beforehand.

How does dry-run flag detection work for CLI command testing?

Dry-run flag detection intercepts CLI commands to switch execution into a simulation mode. It processes the command context to log all simulated writes and state mutations, ensuring no real changes occur while generating a preview summary.

What is the best way to validate development workflows without risking production state?

The best way to validate workflows without risking production state is using full dry-run simulation. It applies read-safe analysis to predict outcomes and logs all side effects, including YAML mutations and agent spawns, to guide real runs safely.

Are there limitations to simulating state mutations and file edits in a dry run?

Limitations exist because dry-run simulation projects state mutations and logs file edits without actual execution. Complex, dependent side effects from real external systems might not be fully captured in the simulated preview summary.