Add Gemini styleguide to fine tune code reviews #4073
Merged
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
jmg-duarte
reviewed
Jan 20, 2026
jmg-duarte
approved these changes
Jan 20, 2026
Contributor
Author
|
/gemini review |
MartinquaXD
approved these changes
Jan 21, 2026
Contributor
There was a problem hiding this comment.
Just leaving my 2ct. Feel free to ignore and instead merge quickly to experiment and iterate rather than letting us argue over our guesses how some wording might result in different behavior.
In other words: I don't have much confidence that we'll know upfront what a good style guide actually is.
The instructions seem very reasonable, though.
fafk
approved these changes
Jan 21, 2026
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
This PR adds a Gemini
styleguide.mdfile to fine-tune code reviews. Right now it can post useless and praise comments (e.g #4072). This style guide should fix this.