From f6aa8f70f4958c57453b945de8f7d2b9a3a1ae9b Mon Sep 17 00:00:00 2001 From: Coco Sheng Date: Thu, 9 Apr 2026 15:04:32 -0400 Subject: [PATCH] docs(triage): explicitly forbid skipping vagueness checks for complex bugs --- .gemini/skills/github-issue-triage/references/triage_rules.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.gemini/skills/github-issue-triage/references/triage_rules.md b/.gemini/skills/github-issue-triage/references/triage_rules.md index d03134be45..79d1f17ca8 100644 --- a/.gemini/skills/github-issue-triage/references/triage_rules.md +++ b/.gemini/skills/github-issue-triage/references/triage_rules.md @@ -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.