Fleet-wide code migrations across hundreds of repos
A background agent applies the same change to many repositories, verifies each build, and opens PRs for owning teams.
The use case
Platform teams that own a shared library must get hundreds of repos to adopt each breaking change. Spotify wrote about Honk, a background coding agent plugged into its fleet management system. Engineers describe a migration in a prompt, the agent applies it to each repository, runs builds and tests, and opens pull requests that owning teams review. Spotify reported more than a thousand merged PRs and highlighted the work of writing good prompts and verification steps. Owning teams still review and merge their PRs, and the platform team watches failure rates and pauses rollouts when something goes wrong.
Example workflow
- Describe the migration and success checks
- Select target repositories
- Agent applies the change and runs verification per repo
- Open PRs to owning teams
- Monitor merge and failure rates and adjust the prompt
Tools
- Spotify Fleet Management
- GitHub
- CI
Risks and guardrails
- A bad prompt multiplies across the fleet; pilot on a few repos
- Verification must be strong because reviewers skim
- Track and roll back if regressions appear
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Spotify Engineering: background coding agent (Honk): engineering.atspotify.com/2025/11/spotifys-background-coding-agent-part-1
- GitHub MCP server (official page): github.com/github/github-mcp-server (checked 2026-11-09)