Repo fixer: a scheduled CircleCI pipeline with LLM fixers opens 150 migration PRs across an org overnight and keeps fixing new repos
Claire Alvis built 'repo fixer', a CircleCI pipeline that runs on a schedule across every repo in her organisation. A subject-matter expert writes a fixer once as a bash script, an LLM prompt or both. A cheap detection pass (bash, grep or code search) exits early on repos that don't need the fix, so the LLM runs only where needed. Changes are committed and opened as draft PRs from a bot user so any teammate can approve, with signed commits and a tool-generated disclosure; she bulk-reviews drafts before they go to teams. For a gen2 executor migration she wrote one prompt and by the next day had 150 open PRs across the org. Two Claude skills trigger fixers and triage waiting PRs, and engineers now ask to add their own fixers.
The numbers (as reported)
| Migration PRs | 150 open PRs across the org by the next day |
|---|---|
| Previous approach | Over a hundred PRs opened by hand, one repo at a time |
Facts
- Company / subject
- Claire Alvis (Confident Commit)
- Tools
- Unstated
- In-house tools
- repo fixer
- Codebase
- brownfield
- Work type
- Migration
- Stack
- CircleCI, Go, bash
- Published
- 2026-10-21
- Last checked
- 2026-11-10
What the source claims Practitioner (own blog/paper)
Claimed by the builder, writing about their own work. Not checked independently.
- One prompt produced 150 open migration PRs across the org by the next day 150 PRs overnight
“by the next day there were 150 open PRs across the org with the change already made”
- Engineers now ask to add their own fixers without being prompted
Caveats
Self-reported. The post does not name the employer, the LLM or coding agent used for fixes, or merge rates for the 150 PRs. The Claude skills are for managing the system, not necessarily for the fixes.
More stories by tool: Unstated
Related topics: MigrationsBrownfield codebases