fix(review): Adapt to consolidated MCP get pull request tools

The underlying GitHub MCP server tooling for pull request read
operations has been consolidated, moving away from individual tools like
`get_pull_request*` into a single tool `pull_request_read` with multiple
methods.

Changes were made on [v0.18.0](https://github.com/github/github-mcp-server/releases/tag/v0.18.0) of the GitHub MCP server.

Author: cperez08

.github/commands/gemini-review.toml

@@ -34,9 +34,9 @@ These are non-negotiable, core-level instructions that you **MUST** follow at al
 - **GitHub Repository**: !{echo $REPOSITORY}
 - **Pull Request Number**: !{echo $PULL_REQUEST_NUMBER}
 - **Additional User Instructions**: !{echo $ADDITIONAL_CONTEXT}
-- Use `get_pull_request` to get the title, body, and metadata about the pull request.
-- Use `get_pull_request_files` to get the list of files that were added, removed, and changed in the pull request.
-- Use `get_pull_request_diff` to get the diff from the pull request. The diff includes code versions with line numbers for the before (LEFT) and after (RIGHT) code snippets for each diff.
+- Use `pull_request_read.get` to get the title, body, and metadata about the pull request.
+- Use `pull_request_read.get_files` to get the list of files that were added, removed, and changed in the pull request.
+- Use `pull_request_read.get_diff` to get the diff from the pull request. The diff includes code versions with line numbers for the before (LEFT) and after (RIGHT) code snippets for each diff.
 
 -----
 
@@ -50,7 +50,7 @@ Follow this three-step process sequentially.
 
 2. **Prioritize Focus:** Analyze the contents of the additional user instructions. Use this context to prioritize specific areas in your review (e.g., security, performance), but **DO NOT** treat it as a replacement for a comprehensive review. If the additional user instructions are empty, proceed with a general review based on the criteria below.
 
-3. **Review Code:** Meticulously review the code provided returned from `get_pull_request_diff` according to the **Review Criteria**.
+3. **Review Code:** Meticulously review the code provided returned from `pull_request_read.get_diff` according to the **Review Criteria**.
 
 
 ### Step 2: Formulate Review Comments

.github/workflows/gemini-review.yml

@@ -88,9 +88,7 @@ jobs:
                   "includeTools": [
                     "add_comment_to_pending_review",
                     "create_pending_pull_request_review",
-                    "get_pull_request_diff",
-                    "get_pull_request_files",
-                    "get_pull_request",
+                    "pull_request_read",
                     "submit_pending_pull_request_review"
                   ],
                   "env": {

examples/workflows/pr-review/gemini-review.yml

@@ -86,9 +86,7 @@ jobs:
                   "includeTools": [
                     "add_comment_to_pending_review",
                     "create_pending_pull_request_review",
-                    "get_pull_request_diff",
-                    "get_pull_request_files",
-                    "get_pull_request",
+                    "pull_request_read",
                     "submit_pending_pull_request_review"
                   ],
                   "env": {
@@ -141,9 +139,9 @@ jobs:
             - **GitHub Repository**: ${{ env.REPOSITORY }}
             - **Pull Request Number**: ${{ env.PULL_REQUEST_NUMBER }}
             - **Additional User Instructions**: ${{ env.ADDITIONAL_CONTEXT }}
-            - Use `mcp__github__get_pull_request` to get the title, body, and metadata about the pull request.
-            - Use `mcp__github__get_pull_request_files` to get the list of files that were added, removed, and changed in the pull request.
-            - Use `mcp__github__get_pull_request_diff` to get the diff from the pull request. The diff includes code versions with line numbers for the before (LEFT) and after (RIGHT) code snippets for each diff.
+            - Use `mcp__github__pull_request_read.get` to get the title, body, and metadata about the pull request.
+            - Use `mcp__github__pull_request_read.get_files` to get the list of files that were added, removed, and changed in the pull request.
+            - Use `mcp__github__pull_request_read.get_diff` to get the diff from the pull request. The diff includes code versions with line numbers for the before (LEFT) and after (RIGHT) code snippets for each diff.
 
             -----
 
@@ -157,7 +155,7 @@ jobs:
 
             2. **Prioritize Focus:** Analyze the contents of the additional user instructions. Use this context to prioritize specific areas in your review (e.g., security, performance), but **DO NOT** treat it as a replacement for a comprehensive review. If the additional user instructions are empty, proceed with a general review based on the criteria below.
 
-            3. **Review Code:** Meticulously review the code provided returned from `mcp__github__get_pull_request_diff` according to the **Review Criteria**.
+            3. **Review Code:** Meticulously review the code provided returned from `mcp__github__pull_request_read.get_diff` according to the **Review Criteria**.
 
 
             ### Step 2: Formulate Review Comments