feat(orchestrate): pin orchestration brain to Opus via skill model field#65
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesOrchestrate Model Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Add `model: opus` to the orchestrate skill frontmatter so the orchestration reasoning (routing, judging, approval, dispatch decisions) always runs on Opus regardless of the session model — including both the `/maxvision:orchestrate` slash command and `when_to_use` auto-activation paths. Dispatched specialist subagents are unaffected: analyze-candidates still selects model per task (sonnet/haiku/opus). This pins only the main-thread orchestrator brain. The skill remains main-thread, so subagent dispatch (Phase 8) is preserved — unlike converting it to a subagent, which the no-nesting rule would break. No version bump (stays 0.1.2). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Codex Review: Didn't find any major issues. Keep them coming! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
Pin the orchestration brain to Opus regardless of session model by adding
model: opusto theorchestrateskill frontmatter (1 line).When the session runs on Sonnet, the orchestration reasoning (routing, judging, approval gates, dispatch decisions) now always runs on Opus — across both activation surfaces (
/maxvision:orchestrateslash command andwhen_to_useauto-activation).Why this, not a subagent
The original idea was to convert the skill into a subagent to pin the model. That breaks the core function: subagents cannot spawn subagents (no-nesting rule), and the orchestrate flow's Phase 8 dispatches specialist subagents. Keeping it a main-thread skill with
model: opusachieves the model pin while preserving dispatch.Scope
analyze-candidatesstill selects model per task (sonnet/haiku/opus). Per-task cost optimization is preserved.Changes
skills/orchestrate/SKILL.mdmodel: opusin frontmatterNo version bump (stays 0.1.2).
test_orchestrate_anti_skip_wiringpasses (3/3).@codex @copilot @CodeRabbit — please review.
🤖 Generated with Claude Code
Summary by CodeRabbit