We’re building an open-source CLI to make repo setup repeatable
One thing we’ve realized from talking to developers is that the hardest part of working with a repo usually isn’t writing code, it’s figuring out the exact conditions that make the repo reliably runnable in the first place.
Not “it worked once.”
Not “CI passed last week.”
Actually repeatable.
That’s the direction we’re pushing Ota toward:
making the first working run repeatable through repo readiness contracts.
Still early, but the feedback so far has been incredibly useful.
Would genuinely love more eyes from people who’ve dealt with setup drift, painful onboarding, or repos that slowly became impossible to trust.
The "it worked once vs. actually repeatable" framing is the right wedge. Setup drift is one of those problems everyone has felt but no one names cleanly — ota doctor / validate / up reads like the Postgres pg_isready of full repos, which is a useful mental model. One question: are the readiness contracts schema-defined (something a human/LLM agent can both read), or convention-based? Asking because agentic coding tools desperately need a machine-readable "is this repo runnable?" signal, and that feels like a natural second audience beyond human onboarding.
Yes, the readiness contracts are schema-defined and machine-readable.
ota.yamllets a repo declare, in a machine-readable way, what it needs, how it becomes runnable, what “ready” actually means, and which workflow is the intended front door.So instead of setup living in tribal knowledge, README drift, or one-off scripts, you get a contract both humans and agents can read:
ota validatechecks that the contract itself is soundota doctoranswers whether the repo is actually ready right nowota upruns the declared path for getting it thereAgents are the natural second audience. If a coding agent can’t reliably tell what a repo needs, how to start it, or whether it’s actually runnable, it’s still guessing. Ota is designed to replace that guesswork with declared repo truth.
If you want to pressure-test it, share your setup and I can help think through what an Ota contract would look like. We also have examples in our GitHub(I can't post links here for some reason), please have a look.
Happy to help you give it a try.