Hello @jbampton, 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!

Summary of Changes

This pull request focuses on correcting minor spelling and grammatical errors across several documentation and source code files within the mruby project. The changes primarily involve fixing typos and ensuring consistency in terminology, such as changing 'file name' to 'filename' and 'bug fixes' to 'bugfixes'.

Highlights

• Spelling Corrections: Corrected spelling mistakes in documentation files (CONTRIBUTING.md, doc/guides/compile.md, doc/guides/debugger.md, doc/guides/mrbgems.md, doc/mruby3.1.md, doc/mruby3.4.md, mrbgems/mruby-bigint/README-fgmp.md, mrbgems/mruby-bigint/core/bigint.h) and source code (src/error.c, mrbgems/mruby-bin-mruby/tools/mruby/mruby.c).
• Terminology Consistency: Ensured consistent use of 'filename' instead of 'file name' in debugger documentation and error message descriptions.
• Grammatical Improvements: Improved grammar by changing 'bug-fixes' to 'bugfixes' and 'Pre-Conditions' to 'Preconditions'.

Changelog

Click here to see the changelog

• CONTRIBUTING.md
  • Corrected 'bug-fixes' to 'bugfixes'.
• NEWS
  • Corrected 'Playstation Portable' to 'PlayStation Portable' in multiple entries.
• doc/guides/compile.md
  • Corrected 'file name' to 'filename'.
• doc/guides/debugger.md
  • Corrected 'file name' to 'filename' in multiple instances.
• doc/guides/mrbgems.md
  • Corrected 'Pre-Conditions' to 'Preconditions' in multiple sections.
• doc/mruby3.1.md
  • Corrected 'bug fixes' to 'bugfixes'.
• doc/mruby3.4.md
  • Corrected 'Playstation Portable' to 'PlayStation Portable' in multiple entries.
• mrbgems/mruby-bigint/README-fgmp.md
  • Corrected 'bug fixes' to 'bugfixes'.
• mrbgems/mruby-bigint/core/bigint.h
  • Corrected 'bug fixes' to 'bugfixes'.
• mrbgems/mruby-bin-mruby/tools/mruby/mruby.c
  • Corrected 'file name' to 'filename'.
• src/error.c
  • Corrected 'file name' to 'filename' in documentation.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

---

A typo's sting,
A filename's true name rings,
Code's clarity sings.

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. ↩

jbampton deleted the fix-grammar-spelling branch

May 14, 2025 07:32