[feature] Add --with-prefix flag to namespace installed plugins

[juancarlosm]

To prevent filename collisions and improve organization in the .config/opencode/ directory, I propose adding a --with-prefix flag. This will ensure that all files (agents, commands, and skills) belonging to a plugin are namespaced with the plugin's name.

The Problem:

Currently, if two plugins contain a file with the same name (e.g., onboard.md or code-reviewer.md), the installation process leads to file overwrites. Additionally, it's difficult to track which plugin provided which command once they are all mixed in the destination folders.

Proposed Feature:

Add a --with-prefix flag that prepends the plugin name followed by a hyphen to every file and skill folder being installed.

Example Usage:

opkg install github:wshobson/agents --plugins git-pr-workflows --with-prefix

Expected Output:

• Commands: .config/opencode/commands/git-pr-workflows-onboard.md
• Agents: .config/opencode/agents/git-pr-workflows-code-reviewer.md
• Skills: .config/opencode/skills/kubernetes-operations-gitops-workflow/

Benefits:

• Conflict Resolution: Safely install multiple plugins that share common naming conventions for commands or agents.
• Traceability: Users can instantly identify which plugin "owns" a specific configuration file.
• Predictability: Using a standard hyphen (-) ensures compatibility across all operating systems and shells.

PR:

Working on it

[hyericlee]

Thanks, this is a great proposal.

Few thoughts I have in mind:

• Maybe subdir namespacing instead .config/opencode/commands/git-pr-workflows/onboard.md
• Auto prefix only if conflicts found

Proposed auto prefixing behavior:

• No prefixes if all filenames are unique
• On installation of different plugin w/ same filename, both existing and incoming plugins files are all prefixed
• Tier-ed prefixing:
  • If same filename, prefix with plugin name
  • If same filename and plugin name, prefix + repo name
  • If same filename, plugin name, and repo name, prefix + user

Incoming:

@hyericlee/essentials/plugins/git/commands/onboard.md
@hyericlee/essentials/plugins/git/commands/commits.md

Before install:

.opencode/commands/onboard.md (from @hyericlee/essentials/plugins/npm/commands/onboard.md)
.opencode/commands/install.md (from @hyericlee/essentials/plugins/npm/commands/install.md)

After install:

.opencode/commands/npm/onboard.md (from @hyericlee/essentials/plugins/npm/commands/onboard.md)
.opencode/commands/npm/install.md (from @hyericlee/essentials/plugins/npm/commands/install.md)
.opencode/commands/git/onboard.md (from @hyericlee/essentials/plugins/git/commands/onboard.md)
.opencode/commands/git/commits.md (from @hyericlee/essentials/plugins/git/commands/commits.md)

Benefits:

• No need for manual conflict resolution
• No need for extra option

[hyericlee]

Alternate proposal:

• Always prefix with plugin name, tier-ed if needed
• Setting to enable/disable in openpackage.yml

Pros:

• Configurable
• Zero ambiguity

Cons:

• Always nested, potential clutter

[juancarlosm]

I think "Always prefix with plugin name" is the correct way, usually the plugin names gives context to the command name