sonu

{
  "name": "sonu",
  "version": "4.10.0",
  "description": "Make your coding agent work like a senior teammate instead of an eager intern. /sonu:build writes every change in your style and test-first, then hands it back with the riskiest parts flagged before you review. /sonu:ship takes it from working tree to merged PR on its own — collecting every AI reviewer bot enabled on the repo, fixing or answering each finding, looping until clean. Once you trust that loop, /sonu:factory turns your issue tracker into the queue: label a ticket in GitHub Issues, Jira, Linear, or a dependency-free local Markdown store, and the agent specs it, builds it in its own git worktree so several tickets can run in parallel, and — once you review the diff and apply the ship label — takes it through review to a merged PR, reporting plan, progress, and risks back to the ticket the whole way. Run a pass per label, or let /sonu:factory poll watch the queue for you. You approve the spec, the diff, and the ship — nothing merges without your label. It also knows what a good interface looks like: /sonu:interface-review audits a whole screen or flow across accessibility, layout, typography, color, motion, and copy, and those same bars fire automatically while it builds. The discipline lives in 26 skills that auto-apply as it works, and that you can read and edit like any other file: code-standards, tdd, debugging, security, performance, intent-interview, design-tree, model-tiering, self-review, blast-radius, pr-conventions, safe-migrations, infra-standards, observability, seo, interface-review, accessibility, layout, ui-polish, typography, colors, ux-writing, ticket-lifecycle, ticket-triage, classify-tickets, bug-finder. Every skill is plain Markdown you can read, fork, and edit — no runtime, no service to sign up for. Works in Claude Code and Cursor. The local tracker needs nothing but git; GitHub Issues uses the gh CLI, and Jira and Linear use their MCP servers or your own API credentials.",