skills.rest
Herxinsasa
HerxinsasaCOMMUNITY
Explore all skills by this author →
GitHub

qa

Convert conversational bug reports into structured GitHub issues.

1|Updated Apr 22, 2026
Search Tags:#github issues#codebase exploration#bug reporting#github cli#issue breakdown#qa session
One-click install
npx skills add https://github.com/Herxinsasa/Skills-Collector --skill qa-herxinsasa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Herxinsasa/Skills-Collector/tree/main/mattpocock-skills/skills/deprecated/qa
Command: npx skills add https://github.com/Herxinsasa/Skills-Collector --skill qa-herxinsasa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of turning informal bug reports and user feedback into structured, actionable GitHub issues, so users don't need to understand internal codebase structure or issue formatting best practices.

Core Features & Use Cases

  • Lightweight Clarification: Asks at most 2-3 short, focused questions to gather missing details without over-interviewing the user.
  • Context-Aware Issue Drafting: Runs background codebase exploration to adopt the project's domain language, ensuring issues remain durable even after major refactors.
  • Intelligent Issue Breakdown: Automatically splits complex reports with multiple independent failure modes into separate, parallelizable issues with clear dependency tracking. Use case: For example, a user reporting that form validation is broken, success messages are missing, and redirects fail will have these split into 3 independent issues that different developers can work on simultaneously.

Quick Start

Use the qa skill to start an interactive QA session where you describe the bug you encountered, and the agent will file a clear, user-focused GitHub issue for it.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I turn informal user bug reports into structured GitHub issues?▼

To convert informal bug reports into structured GitHub issues, you can use a conversational QA session that asks a few clarifying questions and drafts the issue using your project's domain language. This avoids requiring users to understand internal codebase structure or issue formatting.

How do I file a GitHub issue for a bug report with multiple independent failures?▼

Filing a GitHub issue for a bug report with multiple independent failures is handled by automatically splitting the complex report into separate, parallelizable issues with clear dependency tracking. This allows different developers to work on each failure mode simultaneously.

Does filing GitHub issues from user feedback require internal codebase expertise?▼

Filing GitHub issues from user feedback does not require internal codebase expertise. The process runs background codebase exploration to capture user-facing behavior context and adopts the project's ubiquitous language, ensuring the issues remain durable even after major refactors.

Do I need GitHub CLI access to automate issue creation from QA sessions?▼

You need GitHub CLI access to automate issue creation from QA sessions. The conversational QA workflow relies on the GitHub CLI to directly file the drafted, user-focused issues and to perform the background codebase exploration needed to align with project domain language.

What is the best way to align bug reports with project domain language before filing?▼

The best way to align bug reports with project domain language before filing is through context-aware issue drafting. This approach explores the codebase in the background to adopt ubiquitous language, ensuring the generated GitHub issues accurately reflect the project's terminology and remain durable.

Related Skills

Explore More Software Engineering Skills→
wachawowachawo

qa

Gather user context and codebase insights to create GitHub issues.

Community
Advanced
uutauuta
1

dev-step-all

Execute all remaining steps from split plan files until completion or error.

Community
Advanced
SandroBeatzSandroBeatz

lint-check

Run ESLint and TypeScript type checking on a codebase.

Community
Intermediate
kartikkabadikartikkabadi

qa

Converts conversational bug reports into GitHub issues with reproduction steps.

Community
Advanced