1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
# roba-rust-dispatch.toml -- a committed worker-dispatch config for a Rust
# project, proven on a real backlog run (joshrotenberg/cratesio-mcp, ~15 issues).
#
# Copy to your repo as `roba.toml`; roba discovers it via the config pool
# walk-up, so any invocation in the repo (yours or an agent's) inherits it.
#
# The discipline it models: SAFE BY DEFAULT (with no `--profile`, roba's
# built-in read-only posture applies -- Read/Glob/Grep only), and the POWERFUL
# posture is the NAMED `worker` profile -- an explicit opt-in (`--profile
# worker`), never the auto-applied default.
[]
# Unattended issue dispatch: full tool access, a capable model with an opus
# fallback for the hard fixes, bounded by turn + dollar seatbelts.
#
# max_turns is high on purpose: a real fix can cascade a signature change
# across many call sites (a 14-file change exhausted 40 turns before it could
# gate + commit), so 80 gives headroom; the dollar cap is the real seatbelt.
= true
= "sonnet"
= "opus"
= 80
= 10.0
[]
# Cheap one-shots (trivial docs, surveys). Read-only by default; just a
# cheaper model than `worker`.
= "haiku"
# --- Aliases: single-shot invocations parameterized by an issue number ---
[]
# `roba fix 88` -> embed the issue, dispatch a worker, implement + commit.
# A single roba turn (an alias is width, not depth) -- the multi-step PR
# lifecycle around it is a SKILL, not config.
= ["issue"]
= ["--profile", "worker"]
= """
$(gh issue view ${issue})
Implement this issue and commit. Run fmt/clippy/test first; verify any
counts/names from the CODE, not the issue text.
"""
[]
# `roba design 55` -> a READ-ONLY design exploration. No code written.
# Validated hard: on one real issue it found a tool-name collision AND
# dissolved the issue's false premise in a single pass. A design alias does
# not just design -- it audits the spec.
= ["issue"]
= ["--readonly", "--model", "opus"]
= """
DESIGN PHASE -- read-only, NO implementation code.
$(gh issue view ${issue})
Survey the relevant code, then produce a design proposal: approach, data
sources, input/output, integration, edge cases, and open questions for the
maintainer. Do NOT implement.
"""