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

Aberta
#1,165 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
20/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github, typescript
Domínio
cli, devops, release

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
481
Forks
45
Merge médio
1d 13h
PRs com merge (30d)
91

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de ai-driven-dev/framework

Todas as issues de ai-driven-dev/framework

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.