Cursor bugbot instructions, resolves #397

[Oseltamivir]

Current instructions:

# Review Guidelines
1. Ignore any problems in utils/evals/*
2. If any code end up creating a directory in `/workspace`, it is a critical error and should have the title: "Potential EACCES Error". A file in `/workspace` is ok.
3. If any changed file contains /(?:^|\s)(TODO|FIXME)(?:\s*:|\s+)/, then:
    - Add a non-blocking Bug titled "TODO/FIXME comment found"
    - Body: "Replace TODO/FIXME with a tracked issue reference, e.g., `TODO(#1234): ...`, or remove it."
    - If the TODO already references an issue pattern /#\d+|[A-Z]+-\d+/, mark the Bug as resolved.

Docs from https://cursor.com/docs/cookbook/bugbot-rules

---

Note

Adds concise automated review guidelines for tooling.

• New .cursor/BUGBOT.md defining rules: ignore utils/evals/*, treat creating directories in /workspace as a critical "Potential EACCES Error", and flag TODO/FIXME comments with guidance on issue-linked formatting and auto-resolving when references exist
• New .gemini/styleguide.md mirroring the same checks (with TODO reference wording) for Gemini-driven reviews

^{Written by Cursor Bugbot for commit 76747e1. This will update automatically on new commits. Configure here.}

[gemini-code-assist]

Summary of Changes

Hello @Oseltamivir, 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 introduces a new set of bugbot instructions to enhance the automated code review process. By defining clear guidelines for handling specific code patterns like TODO/FIXME comments and critical errors related to workspace access, the changes aim to improve code quality, maintainability, and consistency across the codebase, directly addressing and resolving issue #397.

Highlights

• New Bugbot Instructions Added: A new file, .cursor/BUGBOT.md, has been introduced to define the review guidelines for the Cursor bugbot. These instructions standardize how the bugbot should identify and report specific code patterns and potential issues.
• Workspace Directory Creation Policy: The bugbot instructions now specify that creating a directory within /workspace is considered a critical error, which should be flagged with the title 'Potential EACCES Error'. Creating individual files in /workspace is permitted.
• Automated TODO/FIXME Comment Handling: The bugbot will now automatically detect TODO or FIXME comments in changed files. Upon detection, it will create a non-blocking bug titled 'TODO/FIXME comment found', prompting developers to replace the comment with a tracked issue reference or remove it. If a TODO comment already references an issue, the bug will be automatically resolved.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 a configuration file for the Cursor Bugbot, defining a set of review guidelines. The instructions are clear and well-defined. I have one suggestion to enhance the consistency of a rule and to adhere to a common file formatting best practice.