command prefixes created with /elixir-phoenix:init

[barquesurlocean]

Plugin v2.13.0's init skill writes shortened "/phx:" prefixes into CLAUDE.md while the plugin itself ships its commands as skills under the long name, eg. /elixir-phoenix:work . Claude code flags the shorthand names as unknown.

[oliver-kriska]

Replying as Oliver's Claude Code — Oliver will follow up himself.

Thanks for the precise report — you diagnosed it exactly right, and it was a real bug.

Claude Code namespaces plugin commands by the name in the plugin manifest, not by the install name. Through v2.14.3 that manifest said "name": "elixir-phoenix", so every command resolved as /elixir-phoenix:work while /phx:init wrote /phx:* into CLAUDE.md. The plugin has never shipped a commands/ directory — the prefix was always skill-derived — so this was wrong for the whole v1/v2 line, not just v2.13.0.

It's fixed in v3.0.0. The manifest is now named phx, which is what makes /phx:* correct. The install name stays elixir-phoenix, and two small compatibility plugins restore /ecto:* and /lv:*.

Please don't upgrade with a plain /plugin update

Your report sent me to check the upgrade path, and I found a second problem that I think is the more useful half of this issue.

v3 declares ecto and lv as manifest dependencies. claude plugin update does not install dependencies that a new version newly declares, and a missing dependency is a hard load failure. So updating in place gives you this:

claude plugin update elixir-phoenix@oliver-kriska
✔ Plugin "elixir-phoenix" updated from 2.13.0 to 3.0.1

claude plugin list
❯ elixir-phoenix@oliver-kriska
  Status: ✘ failed to load
  Error: Dependency "ecto@oliver-kriska" is not installed

That takes down all 36 /phx:* commands, not just the three compatibility ones — strictly worse than the prefix mismatch you have now. I reproduced it on Claude Code 2.1.234 in an isolated config directory, so it is not version-specific, and nothing self-heals because auto-update is off by default for non-Anthropic marketplaces.

The upgrade that works

Install the two compatibility plugins first, then update:

claude plugin marketplace update oliver-kriska
claude plugin install ecto@oliver-kriska
claude plugin install lv@oliver-kriska
claude plugin update elixir-phoenix@oliver-kriska

Restart Claude Code, then confirm /phx:help, /ecto:n1-check and /lv:assigns all resolve. Run /phx:init --update afterwards to refresh the CLAUDE.md block.

If you already updated and hit the failure, you don't need to reinstall — just add the two plugins:

claude plugin install ecto@oliver-kriska
claude plugin install lv@oliver-kriska

(claude plugin install elixir-phoenix@oliver-kriska also repairs it, but resolves only one missing dependency per run, so it takes two invocations.)

What I changed

The staged upgrade was already in the README, but it described the failure as "a missing-dependency state" and sat below the fold — which is the same as not saying it, since you're the second person to land here. On main now:

• the upgrade block leads with a warning, states the blast radius in commands lost, adds the recovery path above, declares the 2.1.110 Claude Code floor, and explains the /phx: vs /elixir-phoenix: history for anyone who searches the old prefix
• the release tooling now requires upgrade-breaking releases to open with that warning instead of burying it in a changelog bullet
• make validate checks all five plugin/marketplace manifests instead of two

Those are up in #136. Leaving this issue open until they ship in a release.

Thanks again — the second bug was worth more than the first one.