dryrun-dev

Execute STI agent blocks in a dry-run workspace with synthetic data.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gapfDev/workflow --skill dryrun-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dryrun-dev
Source: https://github.com/gapfDev/workflow/tree/main/.claude/skills/dryrun-dev
Command: npx skills add https://github.com/gapfDev/workflow --skill dryrun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev teams need a safe, repeatable mechanism to run STI agent blocks in a simulated environment, executing each step exactly as written and avoiding any real workspace side effects.

Core Features & Use Cases

  • Deterministic dry-run execution of STI agent blocks with synthetic data.
  • Path redirection and workspace isolation to temp/dryrun/{V}/[ticket-id]/ to prevent real I/O.
  • Full artifact generation for QA gates, mem and dashboard outputs for audits.

Quick Start

Run the dry-run for the agent file and verify deterministic outputs in the temp/dryrun/{V}/[ticket-id]/ workspace.

Frequently Asked Questions about dryrun-dev

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

FAQPage Schema
How do I run deterministic dry-run tests for agent blocks without real I/O side effects?

To run deterministic dry-run tests without real I/O, automate STI agent block execution using a synthetic dataset. This simulates codebase interactions safely by redirecting paths to an isolated workspace, ensuring repeatable outcomes across gates and stopper handling.

What is the best way to isolate agent pipeline testing from the real codebase?

The best way to isolate agent pipeline testing is using a dry-run workspace with explicit path redirection rules. This directs operations to temp/dryrun/{V}/[ticket-id]/, preventing real workspace side effects while executing each step exactly as written.

Can I generate audit artifacts for QA gates during a synthetic dry-run?

Yes, you can generate audit artifacts during a synthetic dry-run. The execution produces full artifact generation for QA gates, alongside mem and dashboard outputs, allowing for thorough quality verification and auditing of the simulated agent interactions.

Do I need a synthetic dataset to simulate agent interactions in testing?

Yes, a synthetic dataset is required to simulate agent interactions in testing. It provides the deterministic data needed to execute STI agent blocks safely without touching real workspace inputs, ensuring consistent outcomes for quality gates.

Why does my agent test produce non-deterministic results across quality gates?

Agent tests produce non-deterministic results across quality gates when real I/O is not properly isolated. Applying path redirection to a dry-run workspace and using a synthetic dataset ensures that execution remains deterministic and repeatable across all gates and stopper handling.