bug-ticket-creator

Convert software defects into structured Markdown bug tickets with reproduction steps.

5|4|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/takusaotome/claude-skills-library --skill bug-ticket-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-ticket-creator
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/bug-ticket-creator
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill bug-ticket-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Bug reports often lack the structured details developers need (repro steps, expected vs. actual results, severity/priority, and environment), which slows down fixes and increases back-and-forth.

Core Features & Use Cases

  • Interactive bug discovery: Gathers what happened, where, and when through guided questions.
  • Reproduction-ready reporting: Collects preconditions, step-by-step actions (CLEAR-style), expected vs. actual behavior, and reproduction rate.
  • QA severity & business priority guidance: Helps determine Severity (technical impact) and Priority (urgency).
  • Professional Markdown output: Generates a standardized Markdown bug ticket using the provided JA/EN templates and a consistent file naming convention.
  • Defect classification with references: Uses defect classification and reproduction/priority guides to structure the report.

Quick Start

Use bug-ticket-creator to generate a Japanese Markdown bug ticket by answering questions about the discovered defect and choosing whether to use the Japanese or English template.

Frequently Asked Questions about bug-ticket-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a structured Markdown bug report with reproduction steps and severity?

Generate a standardized Markdown bug ticket by interactively collecting preconditions, CLEAR-style reproduction steps, expected vs. actual results, and QA severity to structure defect reporting.

What is the best way to standardize QA defect classification and environment details in bug tickets?

Standardize QA defect classification by using built-in reference guides to determine technical severity, business priority, and environment details, outputting a consistent Markdown file for regression workflows.

Can I generate Japanese and English Markdown templates for software testing bug tickets?

Yes, you can generate bug tickets using either Japanese or English Markdown templates, ensuring standardized file naming conventions and clear evidence reporting for system testing workflows.

How do I determine severity and priority when reporting a software defect?

Determine severity and priority during interactive bug discovery; the process guides you through evaluating technical impact for severity and business urgency for priority using defect classification references.

What should I include in a bug ticket to make it reproduction-ready for developers?

Include preconditions, step-by-step CLEAR-style actions, expected vs. actual behavior, reproduction rate, and environment details to make a bug ticket reproduction-ready and reduce developer back-and-forth.