Follow up Rovo Dev upstream updates: event hooks (eventHooks in ~/.rovodev/config.yml)

[dyoshikawa]

Summary

Atlassian's Rovo Dev CLI added an event-hooks system (managed via /hooks, stored in the eventHooks section of ~/.rovodev/config.yml) that rulesync's rovodev target does not implement at all. Separately, the skills adapter still drops the standard compatibility frontmatter field on round-trip (a residual of #1696).

Recent Releases

• Event hooks announcement (2026-01-26): https://www.atlassian.com/blog/development/streamline-rovo-dev-cli-with-event-hooks
• /hooks command ("Manage event hook configurations"): https://support.atlassian.com/rovo/docs/rovo-dev-cli-commands/
• Confirmed present in v0.13.46: https://community.atlassian.com/forums/Rovo-questions/Is-there-any-document-about-the-hooks-command-in-the-Rovo-Dev/qaq-p/3195370

Gaps

• hooks — unsupported. Rovo Dev CLI now has event hooks configured in an eventHooks section of ~/.rovodev/config.yml. Documented event(s) include on_tool_permission (when the agent requests tool permission), plus events on response completion and on error ("we're adding more events"). There is no src/features/hooks/rovodev-hooks.ts (every comparable CLI — claudecode, codexcli, geminicli, cursor, qwencode — has one), and rovodev is absent from the hooks feature entirely.
• skills — compatibility dropped on round-trip (minor). RovodevSkillFrontmatterSchema (src/features/skills/rovodev-skill.ts) declares name/description/allowed-tools/license/metadata but not compatibility. Although the schema is z.looseObject, toRulesyncSkill/fromRulesyncSkill map fields explicitly, so the documented optional compatibility field is silently dropped rather than preserved. (The other fields were addressed in Follow up Rovo Dev upstream updates: saved prompts, tool permissions, and skill frontmatter #1696; compatibility remains.)

Proposed Follow-up

• Add a RovodevHooks adapter writing the eventHooks block into global ~/.rovodev/config.yml (global-only, mirroring rovodev-permissions.ts which already merges into the same file and preserves other top-level keys). Caveat: the exact eventHooks YAML schema is not yet officially documented (preview feature surfaced via /hooks help). Confirm the schema against a live /hooks help / config dump before implementing, and start with the documented on_tool_permission event.
• Add compatibility to RovodevSkillFrontmatterSchema and include it in the round-trip mappings alongside license/metadata.

References

• https://www.atlassian.com/blog/development/streamline-rovo-dev-cli-with-event-hooks — eventHooks in config.yml, on_tool_permission.
• https://support.atlassian.com/rovo/docs/rovo-dev-cli-commands/ — /hooks command.
• https://support.atlassian.com/rovo/docs/extend-rovo-dev-cli-with-agent-skills/ — SKILL.md frontmatter incl. compatibility.
• Prior issue: Follow up Rovo Dev upstream updates: saved prompts, tool permissions, and skill frontmatter #1696 (closed) addressed the other skill frontmatter fields.
• rulesync source: no src/features/hooks/rovodev-hooks.ts; src/features/skills/rovodev-skill.ts.

[dyoshikawa]

Partially addressed by #1996 (merged): the skills compatibility round-trip gap is fixed — RovodevSkillFrontmatterSchema and the rulesync rovodev skill section now carry compatibility through both directions, matching the agentsskills/vibe adapters.

The event-hooks adapter remains open and is currently blocked. The eventHooks YAML schema is a preview feature surfaced only through the interactive /hooks command; neither the Atlassian blog nor the settings docs publish the literal key names / nesting for ~/.rovodev/config.yml. Per this issue's own caveat ("Confirm the schema against a live /hooks help / config dump before implementing"), implementing it now would require guessing the schema and risk emitting config Rovo Dev cannot read. Leaving this open until the eventHooks schema can be confirmed against a live config dump.

[dyoshikawa]

Status update (2026-06-24): the skills compatibility round-trip is fixed and merged (#1996). Re-checked the event-hooks slice today: the eventHooks YAML schema for ~/.rovodev/config.yml is still a preview feature surfaced only through the interactive /hooks command - neither the Atlassian blog nor the settings docs publish the literal key names / nesting. Implementing now would require guessing the schema and risk emitting config Rovo Dev cannot read.

Keeping this open as a deliberate tracker until the eventHooks schema can be confirmed against a live config dump / primary source.