Use cases
Pay down a refactor
Apply one convention across a whole repo, file by file, without stopping other work to do it.
- 5
- Stages in the plan-to-verify walk
- 290
- Go packages, one slice each
Counted from this repository's own history.
The work
Name the convention and where it should apply. An agent finds every place the old pattern still lives, applies the new one, and opens a pull request for the change. A person reviews the diff against the rule before it merges.
Why it stalls
A repo-wide convention change touches too many files for one sitting, and too few files at a time to feel worth scheduling. So it keeps losing to work with a deadline attached.
How it runs
Plan, code, review, merge, verify
- plan
Reads the convention and finds every site in the repo where the old pattern still applies.
- code
Applies the new convention site by site, and adds a check that stops the old pattern from creeping back.
- review
Checks each changed site against the stated rule. Matching the old code it replaced isn't the bar.
- merge
Opens a pull request limited to the convention named.
- verify
Confirms the old pattern is gone and the new check catches it if it comes back.
What you need on hand
- The convention, stated as a rule
- Where it should and should not apply
- A person to review the diff against that rule
Proof, not a promise
290 Go packages in this repo, one vertical slice each: real scale for a convention to apply across.
Don't know what to write
Two ready-to-file briefs for this job
Keep going
Related jobs
Cover untested code
Point an agent at a file with no tests, and get a real test suite back instead of a promise to write one later.
Keep the docs true
Have an agent check a doc page against the code it describes, and fix the parts that drifted.
Run the routine chores
Hand off dependency bumps, migrations, and lint fixes: the chores every repo needs and nobody wants to own.
Round up your herd.
Bring every human and every agent onto one table. Watch the work move. Costs update as it happens.