issue-reporter

To create a reproducible bug report package, this Skill guides you through generating a self-contained `.tar.gz` archive containing `README.md`, `repro/`, and `logs/` components. This ensures clear communication and faster resolution when handing off issues to another team.

The best way to triage reproducible issues is to parse the received `.tar.gz` issue package to understand the problem. This Skill provides a structured workflow to verify reproducibility in a controlled environment and analyze the root cause systematically.

Yes, you can use this issue tracking workflow for both roles. It supports both reporter and handler workflows, providing detailed step-by-step instructions and rules for creating issue packages and subsequently receiving, analyzing, and resolving them.

When packaging a bug report for triage, you need to include a `README.md`, a `repro/` directory for minimal reproduction steps, and a `logs/` directory. These are bundled into a compressed `.tar.gz` archive for self-contained issue reporting.

Packaging a reproducible issue helps with debugging by capturing all necessary files, scripts, and environment details into a single archive. This self-contained format allows the handler to quickly reproduce the problem and analyze the root cause without missing context.

No, this Skill does not require any external dependencies to generate issue tracking archives. It operates independently with its own scripts and references to guide the creation and handling of reproducible `.tar.gz` issue packages.