Tab · Build

Verb registry

Your AI opens the PR. You approve the merge. Every action RepoOps takes goes through a typed verb — open_pr (wraps the routing proposer), file_proposal (wraps the brain reflector), raise_alert (fresh) — with a dry-run + rollback gate (K4.D.3) and a durable file-backed queue (K4.D.4) behind it.

Where to find it

  • Source: lib/actions/registry.mjs + lib/actions/verbs/
  • Localhost: Build → Verb queue · pending approvals at the top
  • API: POST /api/actions/<verb> · GET /api/actions/queue
  • Keyboard: ⌘ K then verb or approvals

What it does for you

Three starter verbs cover the loop.open_pr opens a PR with the proposed diff; file_proposal drops a brain proposal under .claude/brain/proposed/; raise_alert posts to Slack or oncall. Composite verbs and verb expansion land in K5.D.
Dry-run + rollback by default.Every verb runs in dry-mode first; if CI flags the diff, the verb rolls back without merging. Table-driven over the registry — adding a verb means adding its row, not threading a new check through call sites.
Multi-agent consensus on shared writes.K4.D.5 delegates to K2.A.3 active-claims so two agents proposing the same file can't race — the second one waits for the first to land or release.

Read more