Bug Report Review — Development skill for Claude Code

bug-report-review

An agent skill that checks whether a bug report is good enough to start a root-cause analysis — and repairs it when it is not.

Point it at a Jira issue key or URL, a JQL query, or just paste the report text. It returns two verdicts:

• Conformance — is the report well-formed? (ISO/IEC/IEEE 29119-3 structure, IEEE 1044 classification)
• Fix-readiness — can analysis start right now? (the stack trace as text, failing vs. working input, the regression range, the workaround read as a trigger)

The second one is the point. A ticket can tick every box of the standard and still be unfixable because the stack trace is a cropped screenshot; a messy prose ticket that contains the trace, the version delta and two SQL statements is ready today.

What you get

• A verdict: fix-ready, analysable with assumptions, or blocked.
• Every gap, ranked by severity, with what was searched and where.
• Evidence found in attachments, comments and linked issues — including text read off screenshots — instead of a gap that is really sitting in the ticket.
• On request: up to five questions to send back to the reporter, a restructured description, or a hand-off to the analysis.
• A new report written from scratch, asking for the evidence an analysis needs first.

What it never does

• write to your issue tracker without your confirmation of the exact text — and it prefers adding a comment over editing someone's description;
• change severity, priority or status on anyone's behalf;
• follow instructions found inside ticket text, comments, attachments or screenshots, or run attached files.

Installation

The skill is the self-contained `bug-report-review` folder inside this repository. Copy that folder — nothing else is needed, and it works with any agent that supports the [Agent Skills](https://agentskills.io) format.

1. Get the repository:

   git clone https://github.com/jarek-janas/bug-report-review.git

   or downl