/rota-bugreport
File rota’s own mistakes upstream, after your explicit yes.
When to use
Use when rota itself misbehaved (a verb exited 70, a refusal was wrong, a skill step contradicted a verb, the watch reported a false state), on “report a rota bug”, “file this upstream”, or when round wind-down or the Stop hook offers recorded mistakes.
Reach for another skill when
- the bug is in your own project, not in rota:
/rota-capture - you need to find the cause of a bug in your own code:
/rota-debug
/rota-bugreport1 open record: rota worker gate exited 70. Draft (redacted; rota version, OS, harness, model attached): title: worker gate exits 70 on a PR with no body Checked l4ci/rota for duplicates: none. File it?
- an issue filed on the rota repo
- the local record in .rota/bugreports.jsonl marked
filed, with the issue URL
Details
Files rota’s own mistakes upstream. rota records them in .rota/bugreports.jsonl while it runs: a verb that fails with an internal error or panic (exit 70) writes a record, and an agent adds one it noticed with rota bugreport add. rota round wind-down and the Stop hook of a solo session print one non-blocking line when records are open. The skill lists them and shows each report redacted (tokens and keys, email addresses, home-directory paths, hostnames, your repo name and remote URL are removed), with the rota version, OS and architecture, harness and model. It searches l4ci/rota for a duplicate (offering a comment instead) and files only after your yes for that report. Bugs in your own project stay with /rota-capture. Nothing is sent in the background.