Get a repo development-ready with openthunder ready
Clone a repo and you usually face a scavenger hunt: which runtimes, which services, which env vars. openthunder ready reads the repo, tells you exactly what it needs, and can prepare it for you. Keyless and deterministic , it inspects config files, it does not run your code to find out.
See the plan
openthunder ready
It detects the repo's "Project DNA" , stack and toolchains (from package.json/lockfiles, .nvmrc, pyproject/uv.lock, go.mod, *.csproj, pom.xml, .tool-versions, Dockerfiles, devcontainer, CI, .env.example) , plus services and required env vars, and prints a step-by-step plan to make the repo development-ready.
Prepare the environment
openthunder ready --apply # run the plan: activate toolchains, install deps, start services
openthunder ready --apply --yes # skip the confirmation preview
OpenThunder is a thin, governed layer over mature tools (mise for runtimes, uv for Python, the devcontainer spec, Docker/Podman for containers); it activates what a repo needs on demand rather than bundling every runtime. Get the plan as data for your own tooling with openthunder ready --json.
Related
- Understand a repo you didn't write , map the architecture once it runs.
- Getting started , install OpenThunder Desktop first.