automaintainer: Improve supercli static documentation: README, CONTRIBUTING…#187
Conversation
Add bun to prerequisites (used by description enhancement pipeline scripts) with note that it is optional. Expand plugin development section with the isolated file convention directory tree and explicit warning not to edit shared files — new contributors frequently miss this constraint.
…flow The Node.js install section showed 'npx supercli uuid self generate' which is a UUID utility command, not a useful first-run experience. Replace with 'skills list' which immediately demonstrates supercli's core value: querying the 5000+ plugin catalog.
The server-plugins-usage-guide.md file exists in docs/ but was not linked from the features index, making it undiscoverable for users browsing the feature documentation. Add it to the feature index table.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR updates documentation across three areas: contributor prerequisites and plugin development guidance in ChangesDocumentation Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
✨ 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 |
Automated maintenance run by automaintainer.
Focus: Improve supercli static documentation: README, CONTRIBUTING, or docs/ files. Make ONE atomic commit with clear summary explaining what documentation was improved and WHY. Use fix:/docs: prefix. Keep it focused and reviewable.
Branch:
am/am-f17c27-tg5vouWhat Changed
Diff:
Summary by CodeRabbit