Skip to content

feat: add OpenPackage support#341

Open
TiagoJacinto wants to merge 1 commit intoEveryInc:mainfrom
TiagoJacinto:add-openpackage-support
Open

feat: add OpenPackage support#341
TiagoJacinto wants to merge 1 commit intoEveryInc:mainfrom
TiagoJacinto:add-openpackage-support

Conversation

@TiagoJacinto
Copy link
Copy Markdown

Enables installation via opkg install compound-engineering-plugin

Adds openpackage.yml manifest for opkg compatibility.

Enables installation via opkg

Adds openpackage.yml manifest for opkg compatibility.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4ebefd8b7d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -0,0 +1,9 @@
name: compound-engineering-marketplace
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Rename package to match the documented install name

If this gets published to OpenPackage, opkg install compound-engineering-plugin will not resolve to it because package-name installs key off openpackage.yml's name, and this manifest registers compound-engineering-marketplace instead. The rest of the repo already identifies the marketplace as compound-engineering-plugin (see .claude-plugin/marketplace.json:2), so users would have to know an unexpected second name to install it.

Useful? React with 👍 / 👎.

@@ -0,0 +1,9 @@
name: compound-engineering-marketplace
version: 1.0.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep OpenPackage version on the repo's release line

If you pack/publish this manifest or add it as a dependency, hardcoding 1.0.0 creates a third root version surface that will immediately drift from the actual release/tag line. The repo is already at 2.34.4 in package.json, and .releaserc.json:19-22 shows semantic-release only writes back CHANGELOG.md and package.json, so openpackage.yml will stay stale and version-pinned opkg install ...@<version> flows will no longer match the repo's real releases.

Useful? React with 👍 / 👎.

@tmchow
Copy link
Copy Markdown
Collaborator

tmchow commented Mar 22, 2026

@TiagoJacinto can you look at the feedback from codex please?

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.

2 participants