feat(skills): add published skill installation from registry#41
Conversation
Introduce registry-based skill installation alongside the existing bundled `oo` skill. Users can now install published skills by package name with interactive selection, explicit --skill flags, or --all. Key changes: - Add registry skill source fetching with auth headers - Add tarball archive extraction for skill packages - Add interactive multi-select prompt for skill picking - Add managed skill metadata and path resolution - Extend install command with -s/--skill, --all, -y/--yes options - Add @clack/core and picocolors dependencies - Update CLI docs in both English and Chinese Signed-off-by: Kevin Cui <bh@bugs.cc>
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Summary by CodeRabbit
WalkthroughAdds support for installing published Codex skills from an npm-like registry alongside the existing bundled "oo" skill. Introduces registry package fetching, tarball download and extraction, managed-skill path/metadata handling, SKILL.md normalization and guidance injection, interactive TTY prompts for multi-skill selection, and test helpers for simulated interactive I/O. Refactors the Estimated code review effort🎯 5 (Critical) | ⏱️ ~120 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
Why: Windows CI uses native path separators, so tests that assert hard-coded POSIX paths fail even though the implementation is correct. What: Replace literal path expectations with node:path.join in the managed skill path and archive extraction tests. How: Keep the runtime code unchanged and make the assertions derive expected paths through the same platform-aware path helper.
Introduce registry-based skill installation alongside the existing bundled
ooskill. Users can now install published skills by package name with interactive selection, explicit --skill flags, or --all.Key changes: