Feat/add gemini ai

[Dargon789]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: f4d94f2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello, 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 integrates Google Workspace developer documentation access for an AI agent. It introduces a new markdown file explaining the purpose of the Google Workspace Developer Documentation Server and defines two AI agent tools for searching and fetching documentation. Additionally, it updates the extension's configuration to reference this new documentation context.

Highlights

• Introduced Google Workspace Developer Documentation: A new GEMINI.md file was added, detailing the purpose and functionality of a server designed to provide AI agents with access to Google Workspace technical documentation.
• Added AI Agent Tools: Two new tools, search_workspace_docs and fetch_workspace_docs, were registered for the AI agent to search and retrieve content from Google Workspace documentation.
• Updated Extension Configuration: The gemini-extension.json file was modified to include a contextFileName field, linking it to the newly created GEMINI.md file.

Changelog

• GEMINI.md
  • Added a new documentation file explaining the Google Workspace Developer Documentation Server and the AI tools it provides.
• gemini-extension.json
  • Updated the configuration to include contextFileName pointing to GEMINI.md.

Activity

• No activity has occurred on this pull request yet.

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 introduces documentation for a Gemini AI extension by adding a GEMINI.md file and configuring it in gemini-extension.json. My review identifies a couple of style and formatting issues that violate the repository's style guide. I've pointed out inconsistent indentation in the JSON file and a missing newline at the end of the new markdown file.

_{Note: Security Review has been skipped due to the limited scope of the PR.}