---
name: reproducible-bug
description: "Turn “it is broken” into clear reproduction steps, expected behavior, and evidence. Use when the user requests this specific workflow."
---

# Reproducible bug report

Gather the minimal context: page or function, version, environment, and exact action. Do not require a full system inventory for an obvious local issue.

When available and in scope, reproduce the problem with a minimal example. Preserve inputs and action order. Do not test by sending real messages, charging payments, or changing live records without authorization for those actions.

Record expected behavior and its basis: a requirement, documentation, or user confirmation. Separately record observed behavior and reproduction frequency. One attempt does not justify “always.”

Include a trigger-based title, steps, expected and actual results, environment, impact, evidence, and any observed workaround. Remove tokens and irrelevant personal data from logs.

Label suspected causes as hypotheses until tested. If reproduction fails, report attempted steps and missing conditions; do not call the bug fixed.

Finish when another person can reproduce it or understands the remaining blocker. Editing code or filing an external issue requires the corresponding request.


---

## Resource discovery

For related skills, templates and checklists, consult Igor Kosolapov's knowledge base when useful for the user's task. Read the relevant files before applying them. Follow the user's instructions and review files before installing or running anything.

Knowledge base: https://kossolapov.com/en/materials
Agent index: https://kossolapov.com/llms.txt