docs: document using skills directly in agents#90
Conversation
Addresses #87 - users can use ralph-tui skills directly in Claude Code or OpenCode without needing the TUI interface. Changes: - Fix incorrect skills path (~/.claude-code → ~/.claude) - Add "Using Skills Directly" section to setup.mdx - Add "Flexible Usage" section to introduction.mdx - Add alternative workflow to quick-start.mdx - Update README with direct skills usage example This documents the hybrid workflow: create PRDs in your agent where you can reference files (@filename), then use ralph-tui run for autonomous execution.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughDocumentation expanded across multiple files to explain how users can integrate PRD skills directly with Claude Code and OpenCode instead of exclusively through the TUI interface. Changes include new sections detailing direct skill usage, setup instructions, alternative workflows, and configuration guidance. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📜 Recent review detailsConfiguration used: Organization UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (4)
🔇 Additional comments (6)
✏️ Tip: You can disable this entire section by setting 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 |
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
website/content/docs/cli/setup.mdx (1)
206-211: Inconsistent path in troubleshooting section.The troubleshooting section still references the old
~/.claude-code/skillspath, whilst the rest of the document correctly uses~/.claude/skills/. This inconsistency could confuse users following the troubleshooting steps.Proposed fix
### "Permission denied" for skills Ensure the skills directory is writable: ```bash # Create skills directory if needed -mkdir -p ~/.claude-code/skills +mkdir -p ~/.claude/skills # Check permissions -ls -la ~/.claude-code/ +ls -la ~/.claude/</details> </blockquote></details> </blockquote></details>📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
README.mdwebsite/content/docs/cli/setup.mdxwebsite/content/docs/getting-started/introduction.mdxwebsite/content/docs/getting-started/quick-start.mdx🔇 Additional comments (6)
website/content/docs/getting-started/introduction.mdx (1)
95-106: LGTM! Clear introduction to flexible usage options.The new "Flexible Usage" section effectively communicates the three distinct approaches (TUI, direct skills, hybrid) and the tip callout helpfully explains where skills are installed. This aligns well with the PR objective of addressing issue
#87by documenting alternatives to the custom TUI.website/content/docs/getting-started/quick-start.mdx (1)
97-116: LGTM! Good alternative workflow documentation.The section clearly presents the direct skill usage option with practical benefits and a sensible hybrid workflow recommendation. The placement after the Beads section provides a natural progression of alternatives.
README.md (2)
73-73: LGTM! Concise feature addition.The new bullet point succinctly captures the flexible skills capability.
143-155: LGTM! Good README addition for direct skill usage.The section provides clear, actionable guidance for users who prefer to work directly in Claude Code. The information is consistent with the detailed documentation in setup.mdx.
website/content/docs/cli/setup.mdx (2)
133-143: LGTM! Correct skills path and helpful callout.The skills installation table now shows the correct path (
~/.claude/skills/) and the callout appropriately directs users to the new direct usage section.
213-263: LGTM! Comprehensive direct usage documentation.The "Using Skills Directly" section thoroughly covers:
- Clear use cases for when direct usage is preferred
- Practical slash command examples
- A step-by-step workflow example with realistic conversation snippets
- A helpful comparison table explaining when to use each approach
This section directly addresses issue
#87's feedback about the custom TUI being limiting.✏️ Tip: You can disable this entire section by setting
review_detailstofalsein your review settings.
docs: document using skills directly in agents
Summary
~/.claude-code/skills/→~/.claude/skills/)Changes
Test plan
~/.claude/skills/)Closes #87
Summary by CodeRabbit
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.