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

Offen
#1,165 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
20/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github, typescript
Bereich
cli, devops, release

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
TypeScript
Sterne
481
Forks
45
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
91

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ai-driven-dev/framework

Alle Issues in ai-driven-dev/framework

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.