Encourage agent to utilize ecosystem tools to perform work

[gundermanc]

Summary

Fixes an issue where Gemini CLI attempts to manually perform work that can be better done by a tool. If the tool is part of the project config it often does the right thing already. This change corrects for the scenario where the project doesn't provide a script or the script provided doesn't explicitly pass --write or equivalent.

Related Issues

Fixes #15032

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello @gundermanc, 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 evaluation test designed to assess the capability of an automated agent to perform code style fixes using external tools. Specifically, it validates whether the agent can correctly invoke eslint --fix through a shell command to resolve predefined linting issues in a simulated project environment.

Highlights

• New Evaluation Test Added: A new evaluation test file, evals/automated-tool-use.eval.ts, has been introduced to assess the agent's ability to use automated tools for code style fixes.
• ESLint --fix Validation: The test specifically validates that the agent can correctly invoke eslint --fix via the run_shell_command tool to resolve common linting issues like incorrect quotes and missing semicolons.
• Simulated Project Setup: The test sets up a mock project environment including package.json, .eslintrc.json with specific linting rules, and JavaScript files containing deliberate style violations to be fixed.

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

The pull request introduces a new test case for automated tool use, specifically for ESLint --fix functionality. The test setup correctly defines package.json and .eslintrc.json with rules that are violated by the provided src/file1.js and src/file2.js. The assertion logic accurately verifies that the run_shell_command tool is used with eslint --fix. The changes are well-implemented and serve their intended purpose without introducing any high or critical severity issues.

[github-actions]

Size Change: +186 B (0%)

Total Size: 23.7 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.7 MB	+186 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}