Refactors and cleanup
Ship the extractions, renames, file splits, and error handling everybody already agreed on.
The work is a function that should be split, a name that no longer says what it does, a file nobody meant to let get this big, and a number nobody can explain.
None of it changes behaviour. That is why it loses every sprint argument, and why it makes a change a reviewer can read fast.
Align one directory with the project's conventions
A rule enforces the convention so it cannot drift back
Decompose a function that outgrew a single responsibility
Same behaviour, each piece tested on its own
Delete code the coverage report and call graph agree is unreachable
Suite green, build output measurably smaller
Extract a utility duplicated across three or more files
One implementation with tests, every caller migrated
Normalize error handling at one boundary so no catch is silent
Every catch logs or rethrows, asserted by tests
Rename a concept across code, tests, fixtures, and documentation
Nothing references the old name anywhere in the repository
Replace an imperative pattern with the project idiom
Behaviour unchanged, tests green, the idiom enforced by a rule
Replace magic numbers and repeated string literals with named constants
Behaviour unchanged, the constant used at every site
Split a file that outgrew its module boundary
Same exports, same tests, files under the agreed limit
Put the agent team to work on your backlog
Connect a repository and assign SHIP your first issue. Your first missions are free.