Skip to content

Conversation

@kieranklaassen
Copy link
Collaborator

Summary

  • Bare plugin names (e.g., compound-engineering) now always fetch from GitHub
  • Only explicit paths (./plugin, /path/to/plugin, ~/plugin) resolve locally
  • Fixes bug where a same-named local directory would shadow the GitHub fetch

The Bug

Running bunx @every-env/compound-plugin install compound-engineering --to codex from ~ would find ~/compound-engineering/ (not a plugin) and fail with:

Could not find .claude-plugin/plugin.json under /Users/kieranklaassen/compound-engineering

Test Plan

  • New test: bare name ignores same-named local directory, fetches from GitHub
  • All 86 tests pass

Compound Engineered 🤖 Generated with Claude Code

kieranklaassen and others added 6 commits February 12, 2026 13:08
Add converter, writer, types, and tests for converting Claude Code
plugins to Cursor-compatible format (.mdc rules, commands, skills,
mcp.json). Agents become Agent Requested rules (alwaysApply: false),
commands are plain markdown, skills copy directly, MCP is 1:1 JSON.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Previously, `install compound-engineering` would resolve to any local
directory named `compound-engineering` in the current working directory
before trying GitHub. This broke installs when users had a same-named
directory that wasn't a valid plugin.

Now bare names always go to GitHub. Only explicit paths (starting with
./ or / or ~) are treated as local paths.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kieranklaassen kieranklaassen merged commit 20446e9 into main Feb 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant