feat(skills): add laravel-plugin-discovery skill with LaraPlugins MCP#923
Conversation
- Add laraplugins MCP server to mcp-configs/mcp-servers.json - Create laravel-plugin-discovery skill for Laravel package discovery - Supports searching by keyword, health score, Laravel/PHP version - No API key required - free for Laravel community
|
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 (2)
📝 WalkthroughWalkthroughAdded a new MCP server entry Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Agent
participant LaraPlugins as LaraPlugins MCP (https://laraplugins.io)
participant Registry as Composer/Package Registry
rect rgba(200,200,255,0.5)
User->>Agent: Request "find Laravel packages for X"
Agent->>LaraPlugins: SearchPluginTool(query, filters, pagination)
LaraPlugins-->>Agent: Search results (packages, health, compatibility)
Agent->>User: Present shortlisted packages
User->>Agent: Request details for package Y
Agent->>LaraPlugins: GetPluginDetailsTool(package: Y, include_versions?)
LaraPlugins->>Registry: (optional) fetch version history/README
Registry-->>LaraPlugins: package metadata
LaraPlugins-->>Agent: Detailed metrics, compatibility, README, versions
Agent->>User: Show package details and compatibility summary
end
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
No issues found across 2 files
Since this is your first cubic review, here's how it works:
- cubic automatically reviews your code and comments on bugs and improvements
- Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
- Add one-off context when rerunning by tagging
@cubic-dev-aiwith guidance or docs links (includingllms.txt) - Ask questions if you need clarification on any suggestion
Greptile SummaryThis PR adds a
Confidence Score: 5/5Safe to merge — changes are purely additive (new MCP config entry and documentation file) with no runtime risk. All remaining findings are P2 documentation-only style issues in the SKILL.md example and version-label wording. The MCP config entry is correct, consistent with all other HTTP entries in the file, and requires no API key. No logic, security, or correctness issues were found. No files require special attention beyond the two minor documentation nits in Important Files Changed
Sequence DiagramsequenceDiagram
participant User
participant ClaudeCode as Claude Code
participant Skill as laravel-plugin-discovery SKILL.md
participant MCP as LaraPlugins MCP (laraplugins.io/mcp/plugins)
User->>ClaudeCode: "Find a Laravel package for permissions"
ClaudeCode->>Skill: Load skill context
Skill-->>ClaudeCode: Tool names, filters, best practices
ClaudeCode->>MCP: SearchPluginTool({ text_search: "permission", health_score: "Healthy" })
MCP-->>ClaudeCode: List of packages + health indicators
ClaudeCode->>MCP: GetPluginDetailsTool({ package: "spatie/laravel-permission", include_versions: true })
MCP-->>ClaudeCode: Health score, version support, risk score
ClaudeCode-->>User: Recommendation with health + compatibility summary
Reviews (2): Last reviewed commit: "fix(skills): align laravel plugin discov..." | Re-trigger Greptile |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
skills/laravel-plugin-discovery/SKILL.md (1)
159-163: Avoid hardcoded “latest” year labels in compatibility tables.
Latest Laravel (2025)will age quickly. Prefer neutral wording like “newer release line” or remove year-specific recency claims.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/laravel-plugin-discovery/SKILL.md` around lines 159 - 163, Replace the hardcoded year label "Latest Laravel (2025)" in the compatibility table with neutral wording such as "newer release line" or "latest release line" to avoid date rot; update the table row that currently reads `12 | Latest Laravel (2025)` to `12 | newer release line` (or similar), and scan nearby rows (`11 | Current stable`, `10 | Still widely used`, `9 | Legacy but common`, `5-8 | Deprecated`) for any other year-specific phrasing and make them neutral as well.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@mcp-configs/mcp-servers.json`:
- Line 137: Change the invalid transport value by replacing the "type" field
currently set to "streamable-http" with a supported MCP transport type; for the
server entry pointing to "https://laraplugins.io/mcp/plugins" update the "type"
property to "http" so the JSON uses a valid transport ("http", "sse", or
"stdio") and the endpoint is configured correctly.
In `@skills/laravel-plugin-discovery/SKILL.md`:
- Line 11: Rename the section header "## When to Activate" to "## When to Use"
in SKILL.md so the file matches the required skill template; locate the header
text "When to Activate" and replace it with "When to Use" (also update any
internal links or references that point to the old header name if present).
---
Nitpick comments:
In `@skills/laravel-plugin-discovery/SKILL.md`:
- Around line 159-163: Replace the hardcoded year label "Latest Laravel (2025)"
in the compatibility table with neutral wording such as "newer release line" or
"latest release line" to avoid date rot; update the table row that currently
reads `12 | Latest Laravel (2025)` to `12 | newer release line` (or similar),
and scan nearby rows (`11 | Current stable`, `10 | Still widely used`, `9 |
Legacy but common`, `5-8 | Deprecated`) for any other year-specific phrasing and
make them neutral as well.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 95f73bde-804c-4ac0-afe9-c3503d1db11f
📒 Files selected for processing (2)
mcp-configs/mcp-servers.jsonskills/laravel-plugin-discovery/SKILL.md
|
thanks, queued for review. |
feat(skills): add laravel-plugin-discovery skill with LaraPlugins MCP
feat(skills): add laravel-plugin-discovery skill with LaraPlugins MCP
What Changed
Why This Change
Testing Done
Ensured the new skill and mcp are used locally
node tests/run-all.js)Type of Change
fix:Bug fixfeat:New featurerefactor:Code refactoringdocs:Documentationtest:Testschore:Maintenance/toolingci:CI/CD changesSecurity & Quality Checklist
Documentation
Summary by cubic
Adds
laravel-plugin-discoveryskill powered by thelarapluginsMCP to help find and assess Laravel packages. Supports keyword search, health scoring, and Laravel/PHP compatibility; no API key needed.New Features
larapluginsMCP server for plugin discovery (https://laraplugins.io/mcp/plugins).laravel-plugin-discoveryskill with usage guidance and examples.Bug Fixes
SKILL.mdwith MCP tool names and filter options; clarified examples and compatibility notes.Written for commit eac0228. Summary will update on new commits.
Summary by CodeRabbit
New Features
Documentation