qa-bug-ticket-creator

Generate structured bug reports from test failures and create GitHub Issues with duplicate detection.

2|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/AZANIR/qa-skills --skill qa-bug-ticket-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-bug-ticket-creator
Source: https://github.com/AZANIR/qa-skills/tree/main/.cursor/skills/qa-bug-ticket-creator
Command: npx skills add https://github.com/AZANIR/qa-skills --skill qa-bug-ticket-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and templates (resource) components.

What problem does it solve?

This Skill automates the creation of detailed bug reports from test failures or manual findings, streamlining the defect reporting process and preventing duplicate issues.

Core Features & Use Cases

  • Structured Bug Reports: Generates reports with title, expected/actual results, steps to reproduce, evidence, severity, and priority.
  • Duplicate Detection: Searches existing GitHub Issues to avoid creating duplicates before filing a new one.
  • GitHub Issue Creation: Automatically creates GitHub Issues with relevant labels, milestones, and assignees.
  • Use Case: After a Playwright test fails, this Skill can parse the error output, create a comprehensive bug report, check GitHub for similar issues, and file a new issue if none exist, linking to the existing one if found.

Quick Start

Create a bug report from the provided test failure output.

Frequently Asked Questions about qa-bug-ticket-creator

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

FAQPage Schema
How do I automatically create GitHub Issues from test failures?

You can automatically create GitHub Issues from test failures by parsing test output, mapping findings to a standardized bug report template, and integrating with the GitHub API for issue creation and duplicate detection.

How does duplicate detection work when filing bug reports to GitHub?

Duplicate detection works by searching existing GitHub Issues before filing a new bug report to prevent duplicates, linking to the existing issue if a similar one is already found.

Can I generate structured bug reports that include severity and priority?

Yes, you can generate structured bug reports that map test failure findings to a standardized template including severity, priority, title, expected and actual results, steps to reproduce, and evidence.

What test output formats can be parsed for automated defect tracking?

The defect tracking mechanism parses various test output formats, such as Playwright test failure logs, to extract error details and map them into a comprehensive bug report for GitHub Issue creation.

Do I need to configure GitHub API access to automate issue creation?

Yes, you need GitHub API access configured to automate issue creation, apply relevant labels, set milestones, assign users, and search existing repositories for duplicate defects.

What is the best way to track defects without creating duplicate GitHub Issues?

The best way to track defects without duplicates is to automate report generation from test failures and search existing GitHub Issues before creating a new one, linking to the existing issue if matched.