feat(cli): generate and publish each tool's marketplace at release
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 20/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- github, typescript
研究方向
Start with docs/COMPATIBILITY.md and aidd_docs/memory/deployment.md, then inspect the release workflow and the existing plugin sources. Verify each tool's current marketplace and publishing documentation, beginning with Claude Code and Codex, and identify generation and release entry points. Done means each eligible marketplace is generated and published independently at release, unsupported tools are documented with evidence, and a real-tool install is verified.
由索引模型根據 Issue 內容生成。
描述
Problem
The compatibility table (docs/COMPATIBILITY.md) shows a marketplace install for Claude Code, Cursor, GitHub Copilot and Codex, and none for OpenCode, Kilo Code and Antigravity CLI, which only get flat files. A release publishes archives to GitHub Releases and the CLI to npm (deployment memory), and no marketplace online. Users add this repository, which is the development base, not a distribution.
Scope
- For each supported tool whose documentation defines a marketplace or plugin registry, generate its marketplace from the same plugin sources.
- On each release, publish every generated marketplace to the online marketplace that tool offers, with no manual step. Claude Code and Codex are the first candidates.
- Verify per tool, from its current documentation, whether a marketplace and a publishing route exist. Tools without one stay flat and are listed as such.
- Users install and update from the published marketplace, pinned to the released version.
- A failed publication for one tool does not block the others, and is visible in the release run.
- Update the compatibility table from the result.
Acceptance criteria
- Each tool with a documented marketplace gets a generated one, published at release without a manual action.
- Each tool without a marketplace or a publishing route is listed with the evidence.
- An install from the published marketplace is checked on the real tool before it is claimed as supported.
- 主要語言
- TypeScript
- 星號
- 481
- 分支
- 45
- 平均合併
- 1 天 13 小時
- 30 天內合併 PR
- 91
環境準備
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
ai-driven-dev/framework 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 86/100
ai-driven-dev/framework#1311 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 79/100
ai-driven-dev/framework#1244 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
ai-driven-dev/framework#1197 ·
維護者通常 1 天內回覆
-
refactor(aidd-context): apply the new skill template to learn可能已有人在做 @blafourcade 於 3 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
ai-driven-dev/framework#1186 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 83/100
ai-driven-dev/framework#1163 · 1 則留言 ·
維護者通常 1 天內回覆
查看 ai-driven-dev/framework 的全部 Issue
相似的 Issue
-
type: bug
難度 2/5 1-3 小時 新手友好度 78/100
nrwl/nx#37955 · 1 個 reaction ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 67/100
db-ux-design-system/core-web#8856 ·
維護者通常 1 天內回覆
-
'!' breaking change is lost when the commit also has an empty BREAKING CHANGE footer可能已有人在做 @wittdennis 今天認領。 未關閉priority: p3 type: bug
難度 2/5 1-3 小時 新手友好度 74/100
googleapis/release-please#2971 ·
維護者通常 1 天內回覆
-
難度 1/5 1-3 小時 新手友好度 87/100
維護者通常 1 天內回覆
-
🛠️ dette technique
難度 2/5 1-3 小時 新手友好度 61/100
betagouv/mon-entreprise#4752 · 1 則留言 ·
維護者通常 5 天內回覆