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

Aperta
#1,165 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, typescript
Ambito
cli, devops, release

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
TypeScript
Stelle
481
Fork
45
Merge medio
1g 13h
PR unite (30g)
91

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ai-driven-dev/framework

Tutte le issue di ai-driven-dev/framework

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.