qa

Name: qa
Availability: InStock
Author: hgxszhj

Guide users to describe bugs and file GitHub issues with project language.

Updated May 7, 2026

Search Tags:#qa #bug-reporting #github-issues #issue-templates #codebase-exploration #domain-language #interactive-session

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates interactive bug reporting by guiding users to describe problems and enabling the agent to file GitHub issues with durable, user-focused language while exploring the codebase for context.

Core Features & Use Cases

Guided QA session: The agent helps users articulate problems with minimal clarifying questions (2-3).
Background context extraction: The agent explores the codebase to learn domain language and capture relevant context.
Issue creation templates: Generates GitHub issues that are durable and aligned with project language for QA findings.
Scenarios: Use during bug reporting, QA sessions, or when issues are described in natural language.

Quick Start

Describe the issue to the agent and let it file a GitHub issue.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I report a bug and automatically file a GitHub issue from a natural language description?▼

To file a GitHub issue from a bug description, an interactive QA session guides you to articulate the problem with minimal clarifying questions, explores the codebase for domain context, and converts your input into a durable issue template.

What is the best way to create durable GitHub issues that match my software project's domain language?▼

Creating durable GitHub issues aligned with domain language involves exploring the codebase to capture relevant context, then applying that domain vocabulary to structure user-reported problems into issue templates during a guided QA session.

Can I use interactive QA sessions to capture user-reported problems without overwhelming the user?▼

Yes, interactive QA sessions capture user-reported problems by limiting clarifying questions to two or three per issue, ensuring the user is not overwhelmed while still gathering enough detail to file a structured GitHub issue.

How do I convert natural language bug reports into structured issue templates for GitHub?▼

Converting natural language bug reports into issue templates requires an agent to clarify symptoms through a guided session, learn the codebase domain language, and translate the findings into a durable, user-focused GitHub issue structure.

Does filing GitHub issues through an agent require manual codebase exploration for context?▼

No, filing GitHub issues through an agent does not require manual codebase exploration because the agent automatically explores the codebase in the background to learn domain language and capture relevant context for the issue template.

What are the limitations of using interactive sessions for bug reporting?▼

The limitation of using interactive sessions for bug reporting is that the agent restricts clarifying questions to two or three, which may require you to provide highly detailed initial descriptions to ensure all problem symptoms are captured accurately.