VeryGoodOpenSource / VeryGoodOpenSource/vgv-ai-flutter-plugin
feat: add support for Gemini CLI
@ryzizub is already working on this.
Since Jul 21, 2026.
- Dominant language
- Shell
- Stars
- 162
- Forks
- 23
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Description
Gemini CLI (https://github.com/google-gemini/gemini-cli). Tier-2 target under epic #51 alongside Codex.
Gemini CLI is a "universal" agent: it reads .agents/skills/ directly, so once the repo is published to the open standard (#50), skills land in Gemini CLI for free. The remaining work is MCP and hooks.
Scope
- Skills — verified to load from
.agents/skills/and to degrade where a referenced MCP tool is absent (Phase 0). - MCP — wire
dartandvery-good-cliservers via Gemini CLIsettings.json. - Hooks — port the enforcement layer (auto analyze/format, CLI gating) to Gemini CLI hooks. Gemini CLI's hook system mirrors the Claude Code JSON-over-stdin contract and exit-code semantics (same
PreToolUse/PostToolUse/UserPromptSubmit/Stopevents) and ships migration tooling that converts existing Claude Code hooks to its format. - Subagent — Gemini CLI has full subagent support (since v0.36, custom agents as Markdown + YAML frontmatter in
.gemini/agents, close to our existing format). Port theflutter-revieweragent so it dispatches natively. - CI — loader job that installs the skills and asserts they load in Gemini CLI.
Docs: https://geminicli.com/docs/hooks/reference/ and https://developers.googleblog.com/subagents-have-arrived-in-gemini-cli/
Requirements
- Skills load in Gemini CLI via
.agents/skills/ -
dart+very-good-cliMCP wired viasettings.json - Enforcement hooks ported via Gemini's Claude-hook migration tooling
- Gemini CLI loader CI job added
- All CI/CD checks are passing.
- There is no drop in the test coverage percentage.
Additional Context
Part of epic #51. Tier 2 / wave 1 alongside Codex (#46) and OpenCode (#127).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.