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

Abierto
  • ¿Algo no está bien?
#136 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
dart
Área
cli, devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Dart
Estrellas
3
Forks
0
Merge medio
2 d 4 h
PR fusionados (30 d)
40

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de VeryGoodOpenSource/vgv_ai_cli

Todos los issues de VeryGoodOpenSource/vgv_ai_cli

Issues similares

Más issues de Dart

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.