MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-05-14 22:02:59 -07:00
Code Issues Packages Projects Releases Wiki Activity

docs(triage): explicitly forbid skipping vagueness checks for complex bugs

Browse Source
This commit is contained in:
Coco Sheng
2026-04-09 15:04:32 -04:00
parent 21e16eb9f7
commit f6aa8f70f4
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gemini/skills/github-issue-triage/references/triage_rules.md
+2
View File
@@ -125,6 +125,8 @@ Use the JSON output from `analyze_issue.cjs` to determine necessary actions.
- If neither condition is met, proceed to Step 3.
## Step 3: Vagueness Check
**CRITICAL MISTAKE PREVENTION**: You MUST NOT skip this step just because you recognize the problem domain as complex or requiring maintainer attention. No matter how obvious the problem domain might seem, a bug report without explicit, step-by-step reproduction instructions must be halted and marked as vague first.
Is the issue fundamentally missing context AND no one has asked for more information yet?
- **For bugs**: Explicit reproduction steps are **REQUIRED**. Even if the user provides logs, error traces, or screenshots, if they do not provide clear, step-by-step instructions on how to reproduce the bug, it MUST be considered vague.
- **For feature requests**: If it is just a vague statement without clear use cases or details, it is considered vague.