Cross-repo consistency agent. A plain-English change request becomes a fleet-wide migration: watsonx Orchestrate plans, IBM Bob Shell executes per-repo, an aggregator verifies fleet consistency. Real Bob sessions logged.
The brief.
Cross-repo consistency agent. A plain-English change request becomes a fleet-wide migration: watsonx Orchestrate plans, IBM Bob Shell executes per-repo, an aggregator verifies fleet consistency. Real Bob sessions logged.
- What works today
- One plain-English request was applied across three demo repos (Express, Fastify, NestJS), each in its own framework idiom.
- Every IBM Bob session is logged for review.
- What I owned
- orchestration runner, per-repo dispatch, aggregator, dashboard. (solo build)
- Evidence
- SourceLive dashboard
- Known limits
- Shown on one migration across three small demo repos, not a real fleet.
- Production boundary
- Needs runs against real repositories, with review gates and rollback, before time-saving claims.
The problem
Rolling one change across dozens of repos is the kind of tedious, error-prone work that quietly eats senior-engineer time.
What I built
A cross-repo consistency agent. A plain-English change request becomes a fleet-wide migration: watsonx Orchestrate plans it, IBM Bob Shell executes per repo with framework-specific reasoning, and an aggregator verifies the whole fleet ended up consistent. Every Bob session is logged.
The result
One request migrated three frameworks (Express, Fastify, NestJS) with per-repo idiom reasoning, every session captured for review. A week of manual edits becomes a reviewed, auditable run.
This is the kind of internal tool an AI build or retainer produces. More live demos in the AI Lab.
I had a website project and it was handled very gracefully. I'm happy with the work and will be doing more jobs with him. Thank you!
Tayler FreundFounder, BrandWeld
