VeryGoodOpenSource / VeryGoodOpenSource/vgv-wingspan

feat: add support for Gemini CLI

Open
#227 0 comments 0 reactions 1 assignee View on GitHub

@ryzizub is already working on this.

Since Jul 21, 2026.

feature p1
Dominant language
Shell
Stars
105
Forks
15
Avg merge
13h 12m
Merged PRs (30d)
2

Description

Description

Gemini CLI (https://github.com/google-gemini/gemini-cli). Tier-2 target under epic #66 alongside Codex.

Gemini CLI is a "universal" agent: it reads .agents/skills/ directly, so once the repo is published to the open standard (skills.sh), the workflow skills land in Gemini CLI for free. Remaining work is the hook and MCP, plus the subagent-degradation decision.

Scope

  • Skills — verified to load from .agents/skills/.
  • Hook — port recommend-plugins to Gemini CLI hooks. Gemini's hook system mirrors the Claude Code JSON-over-stdin contract and exit-code semantics (same PreToolUse / PostToolUse / UserPromptSubmit / Stop events) and ships migration tooling that converts existing Claude Code hooks.
  • MCP — wire context7 via Gemini CLI settings.json.
  • Subagents — Gemini CLI has full subagent support (since v0.36): custom agents are Markdown + YAML frontmatter in .gemini/agents, with isolated context, curated tools, MCP, and parallel dispatch. Format is nearly identical to our existing agents/*.md, so the review/plan/research panels port with minimal change.
  • CI — loader job asserting skills load in Gemini CLI.

Docs: https://geminicli.com/docs/hooks/reference/

Requirements
  • Skills load in Gemini CLI via .agents/skills/
  • recommend-plugins hook ported via Gemini's Claude-hook migration tooling
  • context7 MCP wired via settings.json
  • Agent definitions placed in .gemini/agents (md+frontmatter); review/plan panels run natively
  • Gemini CLI loader CI job added
Additional Context

Part of epic #66. Tier 2 / wave 1 alongside Codex (#226) and OpenCode (#229).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.