Feat: integrate code review extension in PR workflow instead of using customized review prompt

[cynthialong0-0]

Overview

This PR integrates code review extension (https://github.com/gemini-cli-extensions/code-review) in the PR workflow.

fixes #468

Changes

• Update gemini-review.yml to install code-review extension and prompt to point to code-review instructions
• Update PR workflow readme
• Update related eval tests

Next step

• Cleanup e.g. SetupGithubCommands, generate_examples.sh, gemini-review prompts

[gemini-cli]

🤖 Hi @cynthialong0-0, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[cynthialong0-0]

@gemini-cli /review

[gemini-cli]

🤖 Hi @cynthialong0-0, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[gemini-cli]

🤖 Hi @cynthialong0-0, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[gemini-cli]

🤖 I'm sorry @cynthialong0-0, but I was unable to process your request. Please see the logs for more details.

[cocosheng-g]

@gemini-cli /review

[gemini-cli]

🤖 Hi @cocosheng-g, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[gemini-cli]

🤖 Hi @cocosheng-g, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[cynthialong0-0]

@gemini-cli /review

[gemini-cli]

🤖 Hi @cynthialong0-0, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[cynthialong0-0]

@gemini-cli /review

[gemini-cli]

🤖 Hi @cynthialong0-0, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[gemini-cli]

## 📋 Review Summary

This Pull Request successfully updates the PR review workflow to integrate the dedicated code-review extension instead of using customized local prompts. However, there are a few critical issues with the configuration of the GitHub MCP server in the workflow files that will cause deployment failures and need to be fixed before merging.

🔍 General Feedback

• Docker Environment Variables: The current modifications to how GITHUB_PERSONAL_ACCESS_TOKEN is passed via docker run -e in .github/workflows/gemini-invoke.yml introduces a breakage. Variables inside the args array bypass shell evaluation and are therefore passed as literals rather than pulling the value from the env block.
• Workflow Action References: Make sure any workflow file referencing a testing branch is reverted back to pointing at @main.
• Evals Stability: Relying on runtime HTTP requests to fetch files during evaluation testing can introduce non-deterministic failures. Whenever feasible, favor using mocked local fixtures over remote file downloads to keep evaluations isolated.