feat: Add Gemini Code Assist Customization

Author: cboneti

.gemini/config.yaml

@@ -0,0 +1,11 @@
+have_fun: false
+code_review:
+  disable: false
+  comment_severity_threshold: MEDIUM
+  max_review_comments: -1
+  pull_request_opened:
+    help: false
+    summary: true
+    code_review: true
+    include_drafts: true
+ignore_patterns: []

.gemini/styleguide.md

@@ -0,0 +1,49 @@
+# Cluster Toolkit - Code Review Style Guide for Gemini
+
+When reviewing Pull Requests for the Google Cloud Cluster Toolkit, please adopt the persona of an expert Software Engineer. Your primary focus should be on ensuring changes enhance the project's long-term health. Prioritize the following:
+
+* **Technical Excellence:** Ensure code is well-structured, efficient, and follows best practices.
+* **Maintainability:** Code should be easy to understand, modify, and extend.
+* **Testing:** Changes must be well-tested. Encourage comprehensive unit and integration tests.
+* **Documentation:** Ensure documentation is updated, including in-code comments, module READMEs, and index files.
+
+Pay close attention to the following specifics:
+
+1. **Blueprint Authoring (YAML):**
+    * Ensure the `use` block is preferred for module dependencies within blueprints. Explicit variable linking (e.g., `setting = $(module.output)`) should only be used when necessary to resolve ambiguity.
+    * Verify that module sources are correct and the referenced modules exist.
+    * Check for logical grouping of modules within `deployment_groups`.
+    * Ensure variable usage is correct (e.g., `$(vars.name)`, `$(module.id.output)`).
+    * Validate the overall structure and syntax of the YAML blueprint.
+
+2. **Terraform Module Development (HCL):**
+    * Verify module inputs and outputs are consistent and well-defined.
+    * Check for clear variable definitions in `variables.tf` with descriptions, types, and sensible defaults where applicable.
+    * Ensure resources within the module are logically structured.
+    * Encourage the use of best practices for writing clean and maintainable Terraform code.
+    * Ensure new modules are placed in the correct directory (`modules/` or `community/modules/`).
+
+3. **Go Language:**
+    * Follow standard Go idioms and best practices (e.g., error handling, naming).
+    * Ensure code is well-commented, especially public functions and complex logic.
+    * Check for test coverage for new or modified Go code.
+
+4. **Documentation:**
+    * **CRITICAL:** If new modules (core or community) are added, ensure they are added to the index in `modules/README.md`.
+    * **CRITICAL:** If new examples (core or community) are added, ensure they are added to the index in `examples/README.md`.
+    * In-code comments should be clear and explain the *why* not just the *what*.
+    * Module `README.md` files should be clear and provide sufficient information on usage, inputs, and outputs.
+
+5. **Testing:**
+    * New features or bug fixes should ideally be accompanied by tests.
+    * Tests should be clear and cover both happy paths and edge cases.
+    * Encourage the use of the existing testing frameworks and patterns within the project.
+
+6. **PR Description:**
+    * The PR description should clearly explain the purpose of the change and the problem it solves.
+    * It should mention how the changes were tested.
+
+7. **Structure:**
+    * Confirm adherence to the project structure (e.g., core vs. community).
+
+By focusing on these areas, you can help maintain the quality and consistency of the Cluster Toolkit codebase.