Skip to content

feat: Comprehensive Sage AI code review guidelines from last 100 PRs#5898

Draft
simrankaurb wants to merge 2 commits into
mainfrom
feature/sage-guidelines-100
Draft

feat: Comprehensive Sage AI code review guidelines from last 100 PRs#5898
simrankaurb wants to merge 2 commits into
mainfrom
feature/sage-guidelines-100

Conversation

@simrankaurb

Copy link
Copy Markdown
Contributor

This PR was generated by the Sage Framework to enforce PR best practices by extracting rules from the last 100 merged PRs.

@simrankaurb
simrankaurb requested a review from a team as a code owner July 2, 2026 18:11
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 introduces a configuration file to standardize AI-assisted code reviews across the repository. By explicitly linking the AI reviewer to the project's style guide, the change ensures that future contributions maintain high quality and consistency, reflecting the best practices identified from the last 100 merged pull requests.

Highlights

  • AI Reviewer Configuration: Added a new SKILL.md file to define instructions for the AI code reviewer, ensuring it strictly adheres to the project's established style guidelines.
  • Standardization: Automated the enforcement of best practices by integrating Sage Framework rules derived from the project's historical pull request data.
Ignored Files
  • Ignored by pattern: .gemini/** (1)
    • .gemini/styleguide.md
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 the 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 counterproductive. 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.

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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new SKILL.md file containing code review guidelines for the Cluster Toolkit project. The reviewer noted that the file references a missing .gemini/styleguide.md file, and suggested either including it in the PR or embedding the guidelines directly to avoid broken references.

Comment thread SKILL.md
generated_by: sage_framework
---

You are an expert AI code reviewer. Please read the guidelines defined in the `.gemini/styleguide.md` file located at the root of the project and strictly enforce them during your code reviews.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The file .gemini/styleguide.md referenced here is not included in this pull request. Since the pull request title and description state that this change adds comprehensive code review guidelines extracted from the last 100 merged PRs, please include the .gemini/styleguide.md file in this pull request, or embed the guidelines directly within SKILL.md to avoid broken references.

@simrankaurb
simrankaurb marked this pull request as draft July 2, 2026 18:15
@mufaqam-gcl mufaqam-gcl added the release-chore To not include into release notes label Jul 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-chore To not include into release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants