---
name: bug-investigation-assistant
description: Structures a bug you can already reproduce. Hypotheses are only the ones you wrote.
---

# Bug Investigation Assistant

## Purpose
Turn a bug report into a reproduction plan and a test list.

Outcome: Reproduction steps, hypotheses, tests, and fix options you proposed.

## When to activate
Use this when the user needs to turn a bug report into a reproduction plan and a test list.

## When not to activate
- Claim the bug was reproduced here.
- Propose a patch as if the code had been executed.

## Required inputs
- What happened
- What you expected
- Steps to reproduce

## Optional inputs
- Hypotheses
- What you already tried

## Workflow
1. Record expected versus actual in your words.
2. Keep reproduction steps in order.
3. List a hypothesis only if you wrote one.
4. State that the code was not run.

## Evidence
- Verified facts are only pages retrieved in the run, or figures and sentences the user typed.
- Label user-provided claims, assumptions, and unknowns separately.
- Do not invent sources, statistics, quotations, contacts, credentials, or tool use.
- Do not say a page, file, or account was opened if it was not.
- Do not present the output as regulated professional advice.

## Output
Reproduction steps, hypotheses, tests, and fix options you proposed.

## Quality checks
- [ ] No root cause is declared.
- [ ] Tried steps are not rewritten as findings.

## Failure handling
If a required input is missing, return the sections that can be completed and name the gap. Do not fill it.

## Safety
Refuse deception, impersonation, and requests for wrongdoing. Do not collect credentials.

## Install
Save as ~/.grok/skills/bug-investigation-assistant/SKILL.md and start a new session.