feat: install into a project instead of the user's home

Offen
  • Stimmt etwas nicht?
#136 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
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
dart
Bereich
cli, devtools

Rechercherichtung

Start with the install, doctor and uninstall command entry points and trace how the CLI currently writes harness files and resolves plugin paths. Map each supported harness's project-level files and identify where plugin references, hooks and MCP servers can be translated. Done means project-scoped install, drift detection and noninteractive CI behavior meet the listed requirements, with failures for unsupported translations.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

feature

Description

vgv_ai install writes only to the user's home directory, and skills and agents point at plugin files by absolute path in ~/.vgv_ai/plugins or the Claude Code plugin cache. Nothing it writes can be committed to a repository, so a team can't share one VGV setup through the repo, and CI or a bot that reads the repo can't see it.

npx skills installs at project level, but only skills, and it can't resolve plugin files. At the current tags, Wingspan's 29 shared-file symlinks are skipped (8 of 12 skills affected), and all 5 FFCA skills read ${CLAUDE_PLUGIN_ROOT}/…. Agents, hooks and MCP servers aren't installed at all. VeryGoodOpenSource/vgv-wingspan#270 moves Wingspan to ${CLAUDE_PLUGIN_ROOT} as well, so vgv_ai is the only tool that can translate VGV plugins. This asks it to do that at project level too.

Requirements

  • Add a project scope to install, doctor and uninstall (for example --project [dir]) that writes each harness's project-level files, such as .agents/skills, .codex/, .gemini/settings.json and opencode.json, instead of the home-directory ones.
  • Copy the plugin files that skills and agents reference into the project, for example .vgv_ai/plugins/<plugin>@<tag>/, and rewrite ${CLAUDE_PLUGIN_ROOT} and ${CLAUDE_SKILL_DIR} to paths relative to the repo. No absolute or $HOME paths in the output.
  • Keep the manifest in the project (for example .vgv_ai/manifest.json), with each plugin's tag and a content hash, so doctor can detect drift in CI.
  • Make hooks and MCP servers project-scoped where the harness supports that. Otherwise, record a TranslationNote.
  • Make install --project work without prompts in CI, with an exit code that fails on anything it can't translate.

Additional Context

Use case: a repository that sets itself up for a chosen harness and set of VGV plugins, then commits the result so every contributor, CI and any bot working on the repo share the same setup. Today the only option is to commit the repo's own skills and ask each contributor to run vgv_ai install.

Vorherrschende Sprache
Dart
Sterne
3
Forks
0
Ø Merge
2 T. 4 Std.
Gemergte PRs (30 T.)
40

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 VeryGoodOpenSource/vgv_ai_cli

Alle Issues in VeryGoodOpenSource/vgv_ai_cli

Ähnliche Issues

Weitere Issues zu Dart

Neue Issues direkt in Ihr Postfach

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