Make /review a callable skill instead of a built-in workflow
Open 💬 2 comments Opened May 22, 2026 by stewartadam
What variant of Codex are you using?
CLI
What feature would you like to see?
/review is currently part of the CLI harness and only callable by users. It would be nice if /review was a skill that could be called by agents, so that reviews can be included as a part of workflows defined in AGENTS.md, other skills, or by agents orchestrating other agents.
Additional information
_No response_
2 Comments
I took a quick look at current
origin/main(7d47056). One useful boundary for this request may already exist: the app-server protocol documentsreview/start, and the TUI/reviewflow appears to ultimately route through that RPC.The current flow I found is roughly:
/reviewis parsed asSlashCommand::Reviewin the TUI.AppCommand::review(ReviewTarget::Custom { ... }).AppCommand::Reviewis routed inthread_routing.rstoapp_server.review_start(thread_id, target).AppServerSession::review_startsendsClientRequest::ReviewStartwithReviewDelivery::Inline.ClientRequest::ReviewStarttoturn_processor.rs::review_start/review_start_inner.app-server/tests/suite/v2/review.rs, includingreview_start_runs_review_turn_and_emits_code_review_item.So if the goal is to make review callable by agents or workflows, a smaller implementation path might be to wrap or reuse the existing
review/startapp-server request as the callable surface, subject to whatever boundary the skill/tool system should expose, rather than reimplementing the reviewer as an independent skill from scratch.Ah, workaround: the code review sub-agent is based on the prompt in this file: https://github.com/openai/codex/blob/main/codex-rs/prompts/templates/review/rubric.md
You can just ask Codex to turn that into a callable skill and away you go. I can now ask for
$pr-reviewin other apps like Conductor and it will perform the same high-quality code reviews you get from the Codex CLI.