fix(init): clarify Codex desktop skill usage - #1744
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe PR clarifies Codex onboarding instructions for CLI, IDE extension, and desktop app users. The initialization hint, supporting documentation, tests, and patch changeset now reflect the separate Codex workflows. ChangesCodex onboarding
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change clarifies how users invoke an existing Codex skill in different interfaces without changing runtime behavior, access, or security controls. No actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2 files. (2 skipped: 2 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
alfred-openspec
left a comment
There was a problem hiding this comment.
Verified against the current official Codex skills guidance: CLI and IDE support $ skill mentions, while the desktop app exposes skills through its sidebar. The Codex-only hint preserves the existing behavior for other tools, the single- and multi-tool paths are covered, and all hosted CI and Security checks are green. Approved at 2f32b6e.
Summary
$openspec-proposeis the supported invocation for Codex CLI and IDE.openspec-proposefrom the Skills sidebar.Why
openspec initinstalls Codex skills under.agents/skillsand intentionally skips command files. The existing hint is correct for CLI and IDE, but can be misleading in the desktop app where typing the$...form may not provide an obvious action./opsx-*is not a Codex command.Tests
npm run lint -- --quietnpm run buildnpx vitest run test/core/init.test.ts --reporter=verbosenpx vitest run --silent --reporter=dot --no-colorSummary by CodeRabbit
Documentation
openspec-proposefrom the Codex desktop Skills sidebar.User Experience
Tests