This skill converts a defect description or upstream critique output into a structured bug report suitable for filing in an issue tracker. It extracts artifact, symptom, reproducible steps, expected behavior, and severity, then prepares a clear title and description ready to be created as a tracked issue. The skill prioritizes preserving provenance and avoids duplicate filing.
Use this skill after finding a defect during testing, code review, or when /critique or /review highlights a flaw. Trigger phrases include: "file a bug", "this is broken", or explicit requests to track an issue. It is also useful when converting multiple pipe-format findings into discrete, actionable bug candidates for triage.
This skill is primarily authoring and triage focused and will work with agents that can read repository files and invoke tools for filing issues (GitHub CLI, gh). It fits well with assistant agents that support command-line tool access (e.g., Copilot/Codex/GitHub CLI-enabled agents).
Bug Reporter skill from the tackline workflow suite. Purely instructional SKILL.md with no bundled scripts. Walks through a 5-phase process (detect input → extract details → confirm → file → report) using pipe-format conventions. Clean and well-structured but relies entirely on agent interpretation rather than automated tooling. Task tracker integration is abstract — no specific tracker backend specified.
Part of the tackline workflow suite. Well-designed instructional skill with good safeguards (always confirm before filing, check for duplicates, one bug per issue). No security concerns whatsoever — uses only Read/Grep/Glob tools. Would benefit from example output and a narrower allowed-tools list since it only needs to read code and write to a tracker.