feat: publish Tower as an installable Claude Code plugin#288
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
(optional)There is a line at SKILL.md : ""copy the .mcp.json from the tower-cli repo into your project root...", may be should be now plugin/.mcp.json?
There was a problem hiding this comment.
(optional)
tower skill generateoutput has drifted from the checked-inskills/tower/SKILL.md
plugin/skills/... ?
Add .claude-plugin/marketplace.json cataloguing the Tower plugin, and move the plugin (plugin.json, skills/, .mcp.json) into plugin/ so an install caches only the plugin, not the whole repo.
35fa45a to
ffe5f02
Compare
The repo already had a Claude Code plugin (plugin.json + skills/tower/SKILL.md + .mcp.json) but no way for anyone to install it. A plugin only becomes installable once a marketplace catalog lists it, so this adds one.
Changes
.claude-plugin/marketplace.jsonat the repo root, cataloguing thetowerplugin withsource: "./plugin"plugin.json,skills/,.mcp.json) into aplugin/subdirectory so installing it caches only the plugin, not the entire tower-cli reporegenerate-skillworkflow at the newplugin/skills/tower/SKILL.mdpathplugin.jsonis unchanged: it relies on the default discovery ofskills/and.mcp.jsonrelative to the plugin root, which still resolve after the move.Install flow (once merged to the default branch)
Note
The root
.mcp.jsonmoved intoplugin/. It was not gitignored, so it also auto-loaded thetowerMCP server for anyone doing dev work in tower-cli itself. If that project-scoped behaviour is wanted, we can restore a copy at the root in a follow-up.