Fix OpenCode skill install path

[khaliqgant]

User description

Summary

• install OpenCode skills to the official plural path: .opencode/skills/<name>/SKILL.md
• use registry nested indicators for native nested single-file installs so skill outputs keep SKILL.md
• update OpenCode docs, format metadata, and install tests for the new path

Verification

• npm test --workspace=prpm -- install-file-locations install-multifile
• npm test --workspace=@pr-pm/converters -- to-opencode from-opencode
• npm run typecheck --workspace=@pr-pm/types
• npm run build --workspace=@pr-pm/types
• npm run build --workspace=@pr-pm/converters
• npm run build --workspace=@pr-pm/registry-client
• npm run typecheck --workspace=prpm
• npm test --workspace=prpm
• npm run build --workspace=prpm

---

CodeAnt-AI Description

Fix OpenCode skills to install in the correct folder

What Changed

• OpenCode skills now install to .opencode/skills/<name>/SKILL.md instead of the old .opencode/skill/ path
• Imports from OpenCode now recognize the updated skills folder and keep SKILL.md as the entry file
• Existing OpenCode installs and docs were updated to match the new skill location

Impact

✅ OpenCode skills appear where the app expects them
✅ Fewer broken skill installs in OpenCode
✅ Clearer OpenCode skill setup for users

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[cubic-dev-ai]

No issues found across 11 files

[my-senior-dev-pr-review]

🤖 My Senior Dev — Analysis Complete

👤 For @khaliqgant

📁 Expert in packages/ (220 edits) • ⚡ 7th PR this month

View your contributor analytics →

---

📊 11 files reviewed • 4 high risk • 2 need attention

🚨 High Risk:

• packages/cli/src/commands/install.ts — Core installation function modified, affecting key logic.

⚠️ Needs Attention:

• packages/converters/src/format-registry.json — Changes could break existing functionality if not properly tested with the new directory paths.
• packages/cli/src/commands/install.ts — Additional checks on nestedIndicator and nativeSubtypeConfig required for potential runtime errors.
• +1 more concerns...

---

🚀 Open Interactive Review →

The full interface unlocks features not available in GitHub:

• 💬 AI Chat — Ask questions on any file, get context-aware answers
• 🔍 Smart Hovers — See symbol definitions and usage without leaving the diff
• 📚 Code Archeology — Understand how files evolved over time (/archeology)
• 🎯 Learning Insights — See how this PR compares to similar changes

---

💬 Chat here: @my-senior-dev explain this change — or try @chaos-monkey @security-auditor @optimizer @skeptic @junior-dev

📖 View all 12 personas & slash commands

You can interact with me by mentioning @my-senior-dev in any comment:

In PR comments or on any line of code:

• Ask questions about the code or PR
• Request explanations of specific changes
• Get suggestions for improvements

Slash commands:

• /help — Show all available commands
• /archeology — See the history and evolution of changed files
• /profile — Performance analysis and suggestions
• /expertise — Find who knows this code best
• /personas — List all available AI personas

AI Personas (mention to get their perspective):

Persona	Focus
@chaos-monkey 🐵	Edge cases & failure scenarios
@skeptic 🤨	Challenge assumptions
@optimizer ⚡	Performance & efficiency
@security-auditor 🔒	Security vulnerabilities
@accessibility-advocate ♿	Inclusive design
@junior-dev 🌱	Simple explanations
@tech-debt-collector 💳	Code quality & shortcuts
@ux-champion 🎨	User experience
@devops-engineer 🚀	Deployment & scaling
@documentation-nazi 📚	Documentation gaps
@legacy-whisperer 🏛️	Working with existing code
@test-driven-purist ✅	Testing & TDD

For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews.

[codeant-ai]

CodeAnt AI finished reviewing your PR.