What problem does it solve? Setting up a local environment for QA and integration testing is slow, error-prone, and repeated every time a fresh checkout or worktree needs a running app. This Skill discovers how a repository runs once, compiles that knowledge into committed entrypoint scripts, and makes every subsequent environment boot a single fast command. ## Core Features & Use Cases - One-time discovery, permanent scripts: Detects the project's stack, services, build chain, and launch command from the repo itself, then generates POSIX sh or PowerShell up/down scripts with locking, reuse checks, and build caching baked in. - Disposable, isolated environments: Provisions backing services as throwaway Docker containers bound to 127.0.0.1 on free ports, with fresh database migration and seeding per environment. - Shared test-env descriptor: Writes a test-env.json descriptor (base URL, services, credential references, browser provider state) that QA and integration-test skills attach to, so every consumer drives the same running instance. - Self-improving repair loop: Any failure or drift during a run is patched back into the scripts, proven by re-running them, and logged in a dated history header. - Use Case: A QA agent needs a running app to test a pull request. On first run the Skill discovers the stack, generates test-env-up.sh, verifies it cold and warm, and provisions the browser provider; every later run reuses the healthy environment in seconds. ## Quick Start Ask the agent to prepare a reusable test environment for this repository so QA and integration tests can attach to a running app.
