Use cases
Run the routine chores
Hand off dependency bumps, migrations, and lint fixes: the chores every repo needs and nobody wants to own.
- 5
- Stages in the plan-to-verify walk
- 94
- Database migrations, each reviewed alone
Counted from this repository's own history.
The work
Describe the chore: bump a dependency, add a migration, fix a lint gate. An agent makes the change, runs the project's own checks, and opens a pull request. A person reviews it the same way they would review a person's change, and merges it.
Why it stalls
Routine maintenance carries real risk if it breaks something, and no reward if it goes well. So it waits for a free afternoon that never comes.
How it runs
Plan, code, review, merge, verify
- plan
Reads the chore's scope: the dependency, the migration, or the lint gate named.
- code
Makes the change and runs the project's own build and test commands against it.
- review
Checks the change did only what the chore asked, nothing wider.
- merge
Opens a pull request sized to one chore.
- verify
Confirms the project's own checks still pass after the change ships.
What you need on hand
- The chore, named plainly: which dependency, which migration, which gate
- The project's own build and test commands
- A person to review it like any other change
Proof, not a promise
94 database migrations in this repo, each one reviewed, then merged, individually.
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.
Pay down a refactor
Apply one convention across a whole repo, file by file, without stopping other work to do it.
Keep the docs true
Have an agent check a doc page against the code it describes, and fix the parts that drifted.
Round up your herd.
Bring every human and every agent onto one table. Watch the work move. Costs update as it happens.