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
Copy file name to clipboardExpand all lines: src/metis/plugins/plugins.yaml
+45-4Lines changed: 45 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,10 @@ general_prompts:
14
14
FILE: {file_path}
15
15
security_review_report: |-
16
16
3. How to Report
17
-
- Return a JSON object with a single key "reviews" mapping to a list of identified security issues.
17
+
- List all identified security issues in a JSON array.
18
18
- Each element must strictly follow this structure:
19
19
[[REVIEW_SCHEMA_FIELDS]]
20
-
- If no identified security issues are found, return: {\"reviews\": []}
21
-
- If no CWE identified, does not guess a number.
22
-
- Ensure the json is valid, without any additional commentary or text outside the json structure.
20
+
- IMPORTANT: If no identified security issues are found, return: {\"reviews\": []}
23
21
24
22
plugins:
25
23
c:
@@ -216,6 +214,49 @@ plugins:
216
214
1. FILE - A source code file
217
215
2. RELEVANT_CONTEXT - information about what these changes do.
218
216
217
+
Your tasks are:
218
+
1. Security Review Scope
219
+
- Review the security implications of the FILE.
220
+
If it is empty, ignore it.
221
+
ruby:
222
+
supported_extensions: [".rb"]
223
+
splitting:
224
+
chunk_lines: 40
225
+
chunk_lines_overlap: 15
226
+
max_chars: 1500
227
+
prompts:
228
+
security_review: |-
229
+
You are a thorough security engineer specializing in Ruby.
230
+
Always tie your identified issues directly to the evidence in FILE_CHANGES, RELEVANT_CONTEXT,
231
+
and ORIGINAL_FILE. Do not introduce new security conclusions that are not supported
232
+
by the specific changes or context provided.
233
+
You will be given:
234
+
1. FILE_CHANGES - a set of code changes with lines marked by “+” indicating what has been added or “-” for removed.
235
+
2. RELEVANT_CONTEXT - information about what these changes do.
236
+
3. ORIGINAL_FILE - The original file before being modified. Use this to understand how changes affect the code. (this may be empty).
237
+
238
+
Your tasks are:
239
+
1. Security Review Scope
240
+
- Review the security implications of the FILE_CHANGES, focusing on lines marked with “+.” or “-” but take into account how they interact with the whole file.
241
+
If it is empty, ignore it.
242
+
security_review_checks: |-
243
+
2. What to Check
244
+
- Look for potential security issues such as:
245
+
- OWASP Top 10 vulnerabilities
246
+
- Hardcoded secrets
247
+
- Insecure use of libraries
248
+
- Do not report on issues that do not affect security.
249
+
validation_review: "Validate the following Ruby review for security concerns."
250
+
snippet_security_summary: "Summarize the security implications of these Ruby code changes."
251
+
attempt_fix: "Based on the issues detected in the Ruby code changes, propose a fix patch. Issues: {issues} Patch: {patch}"
252
+
security_review_file: |-
253
+
You are a thorough security engineer specializing in Ruby.
254
+
Always tie your identified issues directly to the evidence in FILE and RELEVANT_CONTEXT.
255
+
Do not introduce new security conclusions that are not supported by the specific changes or context provided.
256
+
You will be given:
257
+
1. FILE - A source code file
258
+
2. RELEVANT_CONTEXT - information about what these changes do.
0 commit comments