feat(cli): generate and publish each tool's marketplace at release

オープン
#1,165 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github, typescript
領域
cli, devops, release

調査の方向性

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時間
マージ済み PR(30日)
91

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ai-driven-dev/framework のほかの issue

ai-driven-dev/framework の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。