Update extensions docs

[chrstnb]

Summary

Restructure extensions docs

fixes #16170

Details

Related Issues

How to Validate

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello @chrstnb, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances and reorganizes the documentation for Gemini CLI extensions. It introduces new guides on best practices and a dedicated reference for extension management commands and configuration, while also restructuring existing content for better clarity and navigability. The goal is to provide a more comprehensive and user-friendly resource for developers working with Gemini CLI extensions.

Highlights

• New Best Practices Guide: A new document best-practices.md has been added, covering development, security, and release best practices for Gemini CLI extensions.
• Documentation Restructuring: The existing extension documentation has been reorganized into more focused files, including a new reference.md for commands and configuration.
• File Renames: getting-started-extensions.md is now writing-extensions.md, and extension-releasing.md is now releasing.md for improved clarity.
• Navigation Updates: The main documentation index (docs/index.md) and sidebar (docs/sidebar.json) have been updated to reflect these changes and new additions.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request does an excellent job of reorganizing the extension documentation, making it more structured and easier to navigate. The addition of dedicated pages for best practices and a full reference is a great improvement. My review focuses on a couple of incorrect examples in the new documentation that could mislead users, particularly around security and configuration. Addressing these will help ensure the documentation is accurate and promotes correct implementation patterns.

[github-actions]

Size Change: -2 B (0%)

Total Size: 22.3 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	22.3 MB	-2 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}

[anowardear062-svg]

Marketing

[anowardear062-svg]

Payments.csv