Reference · Verb registry

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 (writes a brain proposal file), raise_alert (fresh) - with a dry-run + rollback gate and a durable file-backed queue 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/run · 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 emits an alert event you can wire to Slack or oncall. Composite verbs and verb expansion are on the roadmap.
Dry-run + rollback by default.Every verb ships a preview() dry-run and a rollback(), and a CI test gate refuses to merge a verb that is missing either. 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.The action queue delegates to 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