Converts conversational bug reports into GitHub issues with reproduction steps.
npx skills add https://github.com/kartikkabadi/skills --skill qa-kartikkabadi
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
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.
Use the qa skill to help me report this bug as one or more GitHub issues.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
sr-ai-devAnalyze codebase impact and create GitHub issues via gh issue create.
hojinzsDisplays GitHub Issues grouped by status with priority, size, and blocking relationships.
jwilgerSearch codebases by glob patterns and grep queries to locate files and implementations.
OutlineDrivenConvert user-reported problems into structured GitHub issues with reproduction steps.
