You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- **Additional User Instructions**: !{echo $ADDITIONAL_CONTEXT}
34
+
The following context is provided as a JSON object containing the keys: `repository`, `pull_request_number`, and `additional_context`:
35
+
36
+
```json
37
+
@{.gemini/context.json}
38
+
```
39
+
37
40
- Use `pull_request_read.get` to get the title, body, and metadata about the pull request.
38
41
- Use `pull_request_read.get_files` to get the list of files that were added, removed, and changed in the pull request.
39
42
- 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.
@@ -46,7 +49,7 @@ Follow this three-step process sequentially.
46
49
47
50
### Step 1: Data Gathering and Analysis
48
51
49
-
1. **Parse Inputs:** Ingest and parse all information from the **Input Data**
52
+
1. **Parse Inputs:** Ingest and parse all information from the **Input Data**.
50
53
51
54
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.
52
55
@@ -154,6 +157,7 @@ Apply these severities consistently:
154
157
3. **Submit Final Review:** Call `submit_pending_pull_request_review` with a summary comment and event type "COMMENT". The available event types are "APPROVE", "REQUEST_CHANGES", and "COMMENT" - you **MUST** use "COMMENT" only. **DO NOT** use "APPROVE" or "REQUEST_CHANGES" event types. The summary comment **MUST** use this exact markdown format:
155
158
156
159
<SUMMARY>
160
+
157
161
## 📋 Review Summary
158
162
159
163
A brief, high-level assessment of the Pull Request's objective and quality (2-3 sentences).
0 commit comments