rota

/rota-go

Implement an issue and land it with only gofmt, vet and build; no slow tests, no review.

When to use

Use on “/rota-go 42”, “just do this issue and land it”, “fast track 42” for solo work that should skip slow tests and review. Never inside a round.

Reach for another skill when

  • you want per-task verification, tests and the full review chain: /rota-work
  • the work is already built and you want it reviewed before it lands: /rota-ship
  • several issues run in parallel with workers and a merge gate: /rota-orchestrate
Usually before/rota-capture
/rota-go
Usually afternothing in particular
Exampleillustrative, condensed
/rota-go 42
Claimed #42 on rota/42-fix-timer-badge.
gofmt, go vet, go build: clean.
Merged into main. Landed via /rota-go: slow tests and review skipped.
What changes
  • the fix, merged (or a PR opened per work.mergeStrategy)
  • merge commit or PR body carries the Landed via /rota-go line
Where this example comes from

Details

Fast track for solo work: claims an existing issue, implements it with no brainstorm, plan or TDD, runs only gofmt, go vet and go build, then merges or opens a PR per work.mergeStrategy. The smoke suite, go test and the AI review are skipped on purpose, and the merge commit or PR body says so. Cheap-check failures are fixed before anything lands.

It refuses inside a round: workers keep the worker contract because the orchestrator relies on the gate. Use /rota-work when you want tests and review.

Edit this page on GitHub