ship

Take one piece of work in one repository from "somebody described it" to a traceable, reviewed, checks-green change whose fate the human decided. Use whenever someone wants something in a repository actually changed rather than explained - however casually they put it. "can you sort it", "can you take it", "can we get X on this", "have a look at #12" and "fix it and push it" are all this skill; the person does not have to mention branches, a pull request, review or merging, and the change can be as small as one constant, one string of copy or one dependency bump. Also use when handed an issue number or link to build, or an already-open pull request from this kind of work to carry the rest of the way. It runs the whole cycle in one flow - files the tracker issue, branches in an isolated worktree, implements, gets the diff reviewed, opens the PR, drives CI and review feedback to green - then recaps in plain language and asks once whether to squash-merge and clean up. Do not use for questions, diagnosis or code explanation, for reviewing someone else's existing code, for plans or design proposals, for filing an issue when implementation is explicitly deferred, for throwaway local experiments, or for work spanning several repositories.