Issue Investigation Skill

This skill covers investigation and reproduction — confirming a reported problem is real, finding its root cause, and checking whether a fix already exists. For labeling, prioritizing, and routing issues, see doc-triage-agent.

Step 1: Read the Issue Carefully

Extract:

• What is reported — exact symptom (404, wrong content, rendering bug, etc.)
• Where — URLs, file paths, product versions, or page locations
• Date filed — older issues are more likely already fixed
• Assignees / comments — may indicate in-progress or already-resolved work

Step 2: Reproduce the Problem

Verify the reported behavior before assuming it still exists. Issues are frequently fixed without being closed.