Skip to content

Fix Claude plugin directory packaging - #72

Draft
codejunkie99 wants to merge 1 commit into
mainfrom
feature/claude-directory-packaging
Draft

codejunkie99 wants to merge 1 commit into
mainfrom
feature/claude-directory-packaging

Conversation

@codejunkie99

@codejunkie99 codejunkie99 commented Sep 25, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Add a repository marketplace manifest that points to the GateFlow Claude plugin.
  • Add the canonical .claude-plugin/plugin.json inside the plugin package so Claude can load its components.
  • Correct the plugin's declared license to match the repository's BSL-1.1 license.
  • Replace the install script's placeholder GitHub owner and remove unused path substitution.

Verification

  • Reviewed the plugin and marketplace manifest layout against Claude Code's plugin manifest documentation.
  • Tests were not run.

Note

Fix Claude plugin directory packaging with marketplace and plugin manifests

  • Adds a Claude Code marketplace manifest at .claude-plugin/marketplace.json and a plugin manifest at packages/claude-plugin/.claude-plugin/plugin.json declaring commands, agents, skills, and hooks paths.
  • Updates install.sh to clone from codejunkie99/gateflow-cli and drop the post-install GATEFLOW_CLI_PATH rewrite of plugin.json.
  • Changes plugin license metadata from MIT to BSL-1.1.
  • Behavioral Change: installer no longer creates an installed .env file; it also no longer rewrites the copied plugin.json, so installed copies keep the repo path as-is.
📊 Macroscope summarized 6600ac5. 4 files reviewed, 3 issues evaluated, 2 issues filtered, 1 comment posted

🗂️ Filtered Issues

packages/claude-plugin/.claude-plugin/plugin.json — 0 comments posted, 2 evaluated, 2 filtered
  • line 16: agents is configured as the directory ./agents, but Claude Code's manifest rules explicitly require each agents entry to be an .md file and state that directories are not accepted. The new required plugin manifest therefore cannot load this component configuration, preventing the packaged plugin from loading successfully; list the individual agent Markdown files instead. [ Out of scope (triage) ]
  • line 18: The newly declared hooks file contains a SessionStart handler with "type": "prompt". Claude Code supports only command and mcp_tool handlers for SessionStart, so the GateFlow welcome/onboarding hook cannot run when the packaged plugin starts. Use a supported SessionStart handler type or move the prompt behavior to a supported event. [ Out of scope (triage) ]

"author": {
"name": "GateFlow Team"
},
"source": "./packages/claude-plugin",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 High .claude-plugin/marketplace.json:17

Installing this marketplace entry causes Claude to start node with the nonexistent packages/claude-plugin/servers/gateflow-mcp/dist/index.js, so the GateFlow tools MCP server exits immediately and provides no tools. The package is published via source: "./packages/claude-plugin", but the root build only compiles src and the nested package has no source entrypoint; include or build the referenced dist/index.js before publishing, or point the MCP configuration at an existing built entrypoint.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file @.claude-plugin/marketplace.json around line 17:

Installing this marketplace entry causes Claude to start `node` with the nonexistent `packages/claude-plugin/servers/gateflow-mcp/dist/index.js`, so the GateFlow tools MCP server exits immediately and provides no tools. The package is published via `source: "./packages/claude-plugin"`, but the root build only compiles `src` and the nested package has no source entrypoint; include or build the referenced `dist/index.js` before publishing, or point the MCP configuration at an existing built entrypoint.

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