qa

Convert unstructured bug reports into actionable GitHub issues with codebase context.

88|9|Updated Jul 16, 2020
One-click install
npx skills add https://github.com/docs-plus/docs.plus --skill qa-docs-plus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/docs-plus/docs.plus/tree/main/.agents/skills/qa
Command: npx skills add https://github.com/docs-plus/docs.plus --skill qa-docs-plus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of reporting bugs and filing well-structured, actionable GitHub issues, eliminating the need for users to understand codebase internals or issue formatting best practices.

Core Features & Use Cases

  • Interactive Clarification: Asks targeted follow-up questions to capture bug details without over-interviewing users.
  • Context-Aware Issue Writing: Automatically explores the relevant codebase in the background to use project-specific domain language in issues, avoiding stale internal references.
  • Smart Issue Breakdown: Splits complex multi-symptom bug reports into independent, parallelizable GitHub issues with correct blocking relationships to maximize development efficiency. Use case: If a user reports that form validation fails, success messages are missing, and redirects break after submission, the Skill will create three separate, ordered issues that different developers can work on simultaneously.

Quick Start

Start a QA session to report the bug you encountered when submitting the contact form, and I will file the corresponding GitHub issues for you.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I file GitHub issues from conversational bug reports without knowing issue formatting standards?

Filing GitHub issues from conversational bug reports is handled by converting unstructured user descriptions into actionable issues. The system asks targeted follow-up questions and automatically explores the codebase in the background to use project-specific domain language.

Can I report multiple bugs in one QA session and have them filed as separate GitHub issues?

Yes, reporting multiple bugs in one QA session results in separate GitHub issues. Complex multi-symptom bug reports are split into independent, parallelizable issues with correct blocking relationships to maximize development efficiency.

Do I need to understand codebase internals to report bugs and file GitHub issues?

No, understanding codebase internals is not required to report bugs and file GitHub issues. The system automatically explores relevant codebase areas in the background to capture correct domain language for the issue context.

What is the best way to create actionable GitHub issues from unstructured user bug reports?

Creating actionable GitHub issues from unstructured bug reports is best done through interactive QA sessions. The system asks targeted follow-up questions to capture bug details without over-interviewing users, ensuring durable and refactor-resistant issues.

How does interactive bug reporting handle complex multi-symptom reports for GitHub issue filing?

Interactive bug reporting handles complex multi-symptom reports by breaking them down into parallelizable sub-issues. It establishes accurate blocking relationships between the separate GitHub issues so different developers can work on them simultaneously.