PatchPilot — Dependency-Upgrade Autopilot

The problem. Automated dependency PRs (Dependabot, Renovate) only bump a version number — they don't fix the code the new version breaks. So those PRs pile up unmerged, security patches lag for weeks, and every major upgrade burns hours of manual, repetitive fixing. Detection is a solved problem; remediation is not. The solution. PatchPilot is an agentic dependency-upgrade autopilot. It runs the whole upgrade as a pipeline: it copies the repo, performs the naive upgrade, maps every place the dependency is used across the entire codebase, loads the migration rules, spawns one subagent per module to fix the breaking changes in parallel, verifies the result against the test suite, and produces a merge-ready pull request with migration notes and a before/after report. Target users & interaction. It's built for software teams and maintainers drowning in dependency PRs. They point PatchPilot at a repo (a sample project or a real monorepo) and hit Run in the web console; a live log streams the pipeline as it works, and the results panel shows before/after test counts, the per-module subagents, the dependency footprint, and every change it made — labelled "auto" (mechanical) or "Bob" (semantic). What makes it unique. Most tools stop at detection. PatchPilot does the remediation and proves it: every run ends on a green build, or an honest "needs_bob" flag for changes that can't be made safely by rule alone — it never fakes green. A config file adapts it to any repo layout and verify command (tests or type-check). Impact. On our demo (Express 4 → 5), a naive bump crashed all three services (0 tests passing). PatchPilot applied 6 fixes across 3 services and drove the suite to 11/11 passing — in seconds instead of hours. When IBM Bob performed the same migration end-to-end, it cost ~1.41 Bobcoins: a full major-version upgrade, verified, for a fraction of the manual effort.