blacksmith-testbox

To run tests with CI secrets locally, you can automate safe, repeatable CI validation by provisioning a dedicated testbox. This isolated environment executes commands requiring real CI secrets or services while protecting them during local validation.

Achieving CI environment parity involves dispatching CI workflows and running repository commands from the repo root within a warmed-up testbox. This ensures your local builds, migrations, and tests execute under conditions matching your CI.

To set up and reuse a testbox session, warm up the environment using a configuration file, save the generated ID, then execute subsequent commands with that ID. This preserves the session for multiple runs while maintaining secret protection.

Yes, you can sync local code changes to a remote testbox. The process provides delta-sync between local modifications and the testbox, preserving your repo root execution context for accurate, continuous code validation across repositories.

No specific dependencies are required to run isolated CI workflows. The Skill operates independently to warm up remote testboxes, dispatch CI workflows, and manage repository commands without needing additional component installations.

Use a dedicated testbox when your code validation workflows require real CI secrets or active external services. It is especially necessary for unit, integration, and deployment checks demanding strict parity with CI environments and secure secret access.