feat: Add Gemini Code Assist Customization #4820
Draft
+74
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cboneti
force-pushed
the
feat/gemini-code-assist
branch
2 times, most recently
from
6768282 to
e40a2ce
Compare
Member
Author
|
/gemini review |
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
cboneti
force-pushed
the
feat/gemini-code-assist
branch
from
e40a2ce to
b577b32
Compare
bytetwin
reviewed
Nov 5, 2025
.gemini/styleguide.md
Outdated
| 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`. |
Collaborator
There was a problem hiding this comment.
I think we should define the logical groupings based on module types eg) network, storage, cluster etc
Collaborator
There was a problem hiding this comment.
Logical groups for deployment_groups is not defined. You have only added the folder definitions for modules here - 778c7a0#diff-2d64e32e0ed73fabd653270b96703ac45c54f710133a9ed5882c6d0c6efe6f32L24
Member
Author
There was a problem hiding this comment.
ahh, I see. I am not sure how we should guide it at this point as I am not sure how we can guide an agent to find logical deployment groups...
cboneti
force-pushed
the
feat/gemini-code-assist
branch
from
b577b32 to
70f22ce
Compare
Updates the Terraform module development guidelines to ensure new modules are placed in the correct subdirectory within `modules/` or `community/modules/.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: Add Gemini Code Assist Customization
This PR introduces a customization for the Gemini Code Assist on GitHub to improve the quality and consistency of automated code reviews for the Cluster Toolkit.
By adding a
.gemini/directory with astyleguide.mdand a defaultconfig.yaml, we provide Gemini with specific instructions and context about the Cluster Toolkit's best practices, structure, and documentation requirements.The
styleguide.mdemphasizes:useblock, module sourcing).modules/README.md,examples/README.md) when new modules/examples are added.This customization aims to make Gemini Code Assist reviews more relevant and helpful, catching potential issues early and reinforcing project conventions.