skills.rest
yash-garg
yash-gargCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa

Convert conversational bug reports into structured GitHub issues.

Updated Jun 26, 2026
Search Tags:#debugging#github#qa#issue tracking#codebase exploration#bug reports
One-click install
npx skills add https://github.com/yash-garg/pi-config --skill qa-yash-garg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/yash-garg/pi-config/tree/main/skills/qa
Command: npx skills add https://github.com/yash-garg/pi-config --skill qa-yash-garg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn conversational bug reports into clear, durable GitHub issues by capturing user impact, expected behavior, and reproduction details without unnecessary investigation overhead.

Core Features & Use Cases

  • Interactive QA Sessions: Guides users through lightweight clarification while collecting enough context to report issues effectively.
  • Contextual Issue Creation: Explores the codebase for domain language and creates user-focused GitHub issues that avoid brittle implementation details.
  • Use Case: A developer can describe a broken workflow in conversation, and the Skill transforms the report into one or more actionable issues with proper scope and prioritization.

Quick Start

Ask the qa skill to start a QA session and help file issues for the problems I describe.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I convert conversational bug reports into structured GitHub issues?▼

To convert bug reports into structured GitHub issues, you can start an interactive QA session that guides you through providing user impact, expected behavior, and reproduction details without manual formatting overhead.

How do I file GitHub issues from bug descriptions without including brittle implementation details?▼

To file GitHub issues without brittle implementation details, the skill explores your codebase for domain language and translates user-focused conversational reports into actionable engineering tasks with proper scope.

What is the best way to track software debugging workflows interactively?▼

The best way to track software debugging workflows interactively is running a guided QA session that captures enough context to report problems effectively and transforms them into prioritized GitHub issues.

Can I create multiple actionable GitHub issues from a single broken workflow description?▼

Yes, you can create multiple actionable GitHub issues from a single broken workflow description by describing the problem conversationally, allowing the skill to split the report into properly scoped tasks.

Do I need to manually investigate the codebase before filing bug reports?▼

No, manual codebase investigation is not required before filing bug reports because the skill performs codebase exploration automatically to extract domain language and generate user-focused GitHub issues.

When should I use an interactive QA session for issue tracking?▼

You should use an interactive QA session for issue tracking when you need to capture conversational bug reports with user impact and reproduction details, ensuring software debugging workflows produce durable engineering tasks.

Related Skills

Explore More Software Engineering Skills→
ruskibeatsruskibeats

qa

Create GitHub issues from conversational bug reports with codebase context.

Community
Intermediate
eygrabereygraber
1

add-work

Automates GitHub issue creation and project board organization via Bash scripts and the GitHub CLI.

Community
Intermediate
nseluganseluga

domain-modeling

Collaboratively define and standardize project domain terminology and record architectural decisions.

Community
Advanced
docs-plusdocs-plus
88

qa

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

Official
Intermediate