Understand any codebase before lunch.
New developers lose days — sometimes weeks — just working out how an unfamiliar system fits together. Paste a public GitHub repository and OnboardPilot runs five analyst agents in parallel to produce an onboarding map: architecture, execution traces, house rules, risk radar, three shippable first tasks and a seven-step ramp-up plan.
The difference: every single claim cites the file it came from. Click any citation and verify it on GitHub. No evidence, no claim.
How it works
Five specialists, one shared context, zero invented file paths
Repository context assembly
OnboardPilot pulls the repository tree, ranks the files that actually explain a codebase (docs, manifests, entry points, shallow core modules), and reads them into a single shared context. Build outputs, dependencies and binaries are dropped.
Parallel analyst fan-out
Five agents — Architecture Mapper, Entry-Point Detective, Convention & Risk Radar, First-Task Generator and Ramp-Up Planner — run concurrently against that same context, so they agree on the facts instead of inventing their own.
Verification, not vibes
Every agent must attach the real file paths behind each statement, and declare what it could not determine. The report links each citation straight to GitHub and exports to an ONBOARDING.md you can commit.
Built with IBM Bob 2.0
Bob was the development partner, not a code autocomplete
OnboardPilot was designed, implemented, reviewed and hardened inside IBM Bob IDE. Task session summaries for each of these workstreams are committed under bob_sessions/.
Agent mode
Bob made real, multi-file changes under an approved plan: tightening the repository ranking heuristics in lib/github.ts, hardening the server-sent-events error paths, and adding the guardrails that stop test fixtures crowding out core source.
Plan mode
Bob read the repository, the challenge statement and the submission rules, then produced the hardening plan the rest of the build followed — every item with the files involved, the risk of skipping it and an effort estimate.
Document understanding
Bob read the hackathon guide, challenge statement and submission rules and turned them into the compliance checklist this project was built against — then audited the README against the actual source and listed every claim that did not hold.
Code reviews
The built-in Review workflow analysed lib/github.ts and lib/agents.ts as a staff-engineer sign-off: crafted URL parsing, unbounded reads, missing timeouts and prompt injection from repository content. The findings were fixed, not filed.
Custom rules & .bobignore
Project rules pinned the "always cite a real file path" discipline and the code style; .bobignore kept credentials out of Bob session history from the first commit, and a dedicated security pass covered credential handling and untrusted input.
Task session summaries
Every Bob task that shaped this repository was captured as a task session consumption summary and committed under bob_sessions/ as required evidence.