qa

Name: qa
Availability: InStock
Author: Kartik

Converts conversational bug reports into GitHub issues with reproduction steps.

Updated Jul 17, 2026

Search Tags:#qa #github issues #triage #bug reporting #reproduction steps #issue breakdown

Ready to run

npx skills add https://github.com/kartikkabadi/skills --skill qa-kartikkabadi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/kartikkabadi/skills/tree/main/qa
Command: npx skills add https://github.com/kartikkabadi/skills --skill qa-kartikkabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn conversational bug reports and QA feedback into durable GitHub issues without forcing the user to know the codebase or write a formal ticket.

Core Features & Use Cases

Interactive clarification: Asks a small number of targeted follow-up questions to capture expected vs actual behavior and reproduction details.
Background codebase exploration: Investigates the relevant area of the repository to learn domain language and user-facing behavior boundaries.
Issue filing: Creates concise, user-focused GitHub issues that describe symptoms, expected behavior, steps to reproduce, and useful context.
Breakdown support: Splits multi-symptom reports into parallelizable issues when needed and preserves blocking relationships.

Quick Start

Use the qa skill to help me report this bug as one or more GitHub issues.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I turn conversational bug reports into structured GitHub issues?▼

To turn conversational bug reports into GitHub issues, this Skill asks targeted follow-up questions to capture expected versus actual behavior. It then drafts concise, user-focused tickets containing clear reproduction steps and relevant context without requiring codebase knowledge.

What is the best way to file GitHub issues from multi-symptom bug reports?▼

The best way to file GitHub issues from multi-symptom reports is to clarify and break them down into separate tickets. This Skill splits complex reports into parallelizable issues while preserving blocking relationships, ensuring each ticket captures distinct symptoms and reproduction details.

Do I need to know the codebase to write clear GitHub issues for bug triage?▼

You do not need to know the codebase to write clear GitHub issues for bug triage. This Skill performs background repository exploration to learn the domain language and user-facing behavior boundaries, drafting tickets that describe symptoms without citing internal implementation details.

How does issue triage handle expected vs actual behavior clarification?▼

Issue triage handles expected vs actual behavior clarification through interactive questioning. This Skill asks a small number of targeted follow-up questions during the QA session to capture precise reproduction details and user-facing behavior descriptions before drafting the final GitHub issue.

Can I use this for interactive QA sessions to report user-facing bugs?▼

Yes, you can use this for interactive QA sessions to report user-facing bugs. It applies directly to conversational feedback by asking targeted follow-up questions, exploring the repository background, and generating concise GitHub issues focused on user-facing symptoms rather than internal code.

What are the limitations of automated issue breakdown for complex bug reports?▼

A limitation of automated issue breakdown for complex bug reports is that the resulting tickets focus strictly on user-facing symptoms and reproduction steps. This Skill deliberately omits internal implementation details, meaning tickets may lack root-cause analysis or specific code-level debugging context.