Skip to content

docs(readme): refresh Gemini CLI section to reflect v0.0.11 hook fix#31

Merged
slashben merged 1 commit into
mainfrom
docs/readme-gemini-hook-sync
May 4, 2026
Merged

docs(readme): refresh Gemini CLI section to reflect v0.0.11 hook fix#31
slashben merged 1 commit into
mainfrom
docs/readme-gemini-hook-sync

Conversation

@slashben

@slashben slashben commented May 4, 2026

Copy link
Copy Markdown
Member

Summary

PR #30 made the SessionStart hook portable across Claude Code and Gemini CLI (shipped in v0.0.11). The README's Gemini CLI subsection was never updated to reflect this.

Old:

Add this repo as an extension. The Gemini extension loads the same skills as the Claude plugin from `skills/`. Install the binary first (see the next section).

This is now wrong on two counts:

  1. No actual install command shown.
  2. "Install the binary first" — under v0.0.11, the SessionStart hook auto-installs the binary on first session under Gemini, exactly as it does under Claude.

New:

  • Shows the verified install command (`gemini extension install https://github.com/armosec/armoctl\`).
  • Notes the GitHub-Releases-asset 404 fallthrough and the `git clone` fallback prompt (matches what users actually see, and matches the docs-hub gemini-cli.md).
  • States that the same SessionStart hook handles binary install + version pinning under Gemini.

The matching change in the docs hub (`readme-armo-hub-docs/docs/Integrations/ai-agents/gemini-cli.md`) was pushed live to the `v2.0` branch as commit `94cc42c` since that's the live ARMO docs source.

Test plan

  • `grep -n 'session-start\|SessionStart\|hook\|0\.0\.10\|0\.0\.11' README.md` — no remaining stale references in the Gemini section.
  • After merge: render on github.com/armosec/armoctl, confirm the new code fence renders.

No `release` label — docs-only.

Summary by CodeRabbit

  • Documentation
    • Updated Gemini CLI installation instructions with clearer setup process
    • Added documentation for release-asset 404 fallback behavior with git clone option
    • Documented automatic armoctl binary installation and updates through the extension

The Gemini CLI install instructions were a vague one-liner pointing
at the Install section to install the binary manually first. With
v0.0.11 the SessionStart hook is portable across Claude Code and
Gemini CLI, so the binary auto-installs on the first session under
Gemini exactly as it does under Claude.

- Show the actual 'gemini extension install' command users should run.
- Note the GitHub-Releases-asset 404 fallthrough and the 'git clone'
  fallback prompt (matches what users see today and what the docs
  hub gemini-cli.md describes).
- State that the same SessionStart hook handles binary install and
  version pinning under Gemini — no manual install needed.
Signed-off-by: Ben <ben@armosec.io>
Copilot AI review requested due to automatic review settings May 4, 2026 20:28
@coderabbitai

coderabbitai Bot commented May 4, 2026

Copy link
Copy Markdown
ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: db2c3d45-4888-4f55-a6b9-4d826a946dde

📥 Commits

Reviewing files that changed from the base of the PR and between d84b654 and 00f5291.

📒 Files selected for processing (1)
  • README.md

📝 Walkthrough

Walkthrough

Updated README.md Gemini CLI section with a direct gemini extension install command for armosec/armoctl, details on the 404 release-asset fallback requiring git clone, and notes that automatic binary installation mirrors the Claude Code plugin's skills and SessionStart hook behavior.

Changes

Documentation Update

Layer / File(s) Summary
Installation Instructions
README.md (lines 19–24)
Gemini CLI section now provides direct gemini extension install https://github.com/armosec/armoctl command, explains 404 fallback behavior (answer Y to git clone), and clarifies automatic armoctl binary installation/update via shared skills and SessionStart hook.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

📖 The docs now shine so crystal clear,
With gemini commands right here!
Install with one snap, no need to fear,
The rabbit's written paths, dear reviewer! 🐰


Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

Review rate limit: 1/3 review remaining, refill in 25 minutes and 57 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the README’s Gemini CLI onboarding docs so they match the current cross-agent plugin behavior introduced with the shared SessionStart hook. In the broader codebase, this keeps the public install guidance aligned with the actual Gemini extension manifest and hook-based binary management flow.

Changes:

  • Adds the concrete Gemini extension install command.
  • Replaces the outdated “install the binary first” guidance with the current hook-driven install/update behavior.
  • Documents the current Gemini install fallback flow users see when the release-asset fetch misses and Gemini offers a repo clone.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@slashben
slashben merged commit 7eb4dfd into main May 4, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants