Scan the evidence
Detect manifests, services, ports, environment names, Docker state, and Git safety—deterministically.
Built by team Necromancers
Repo2Prod turns an unfamiliar repository into a verified, reproducible local runtime—without hiding IBM Bob or trusting generated config on faith.
The productionization loop
Local code collects facts. Bob reasons and repairs. Repo2Prod executes every change and only reports what it actually observed.
Detect manifests, services, ports, environment names, Docker state, and Git safety—deterministically.
Run a focused project skill in visible Bob Agent mode to create or minimally repair the runtime.
Build and start Docker Compose, probe the health endpoint, run tests, and capture the true result.
Give bounded, redacted diagnostics back to Bob for the smallest fix—then verify again.
Evidence over confidence
A Dockerfile that looks right is not a running application. Repo2Prod waits for observed build, service, health, and test results before declaring a local runtime ready.
“AI can write the config. Repo2Prod closes the loop between generated code and a runtime that demonstrably works.”
Interprets the codebase, creates runtime configuration, and makes focused fixes.
Runs the software, observes real failures, and proves the result with evidence.
Project artifacts
Download the IBM Bob IDE extension, explore the hackathon presentation, and watch the complete Repo2Prod demo.
Install Repo2Prod directly in IBM Bob IDE.
The story, architecture, product value, and proof behind Repo2Prod.
Watch the golden path: analyze, repair, verify, and generate CI with IBM Bob.
The Necromancers’ spell