Mark the current issue as done
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (repo conventions) and Spec (does it match the originating issue/PRD). Use when the user wants to review a branch, a PR, work-in-progress changes, or asks…
Fix problems pointed out in a code review session.
Apply Uber's Go Style Guide when generating, editing, or reviewing Go code.
Implement a piece of work based on a spec or set of tickets.
Apply behavior-preserving code refactorings from Martin Fowler's "Refactoring" (2nd ed.) catalog. Use whenever the user wants to restructure existing code without changing its behavior — a general cleanup/refactor request, a named Fowler refactoring (Extract…
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.