qa

Convert user-reported bugs into structured GitHub issues via guided QA sessions.

Updated Apr 8, 2026

Search Tags:#feedback #github #qa #issue tracking #software testing #bug reporting

Ready to run

npx skills add https://github.com/tonomb/personal-pnl --skill qa-tonomb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/tonomb/personal-pnl/tree/main/.agents/skills/qa
Command: npx skills add https://github.com/tonomb/personal-pnl --skill qa-tonomb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bridges the gap between informal user feedback and structured project management by automatically converting conversational bug reports into high-quality, durable GitHub issues.

Core Features & Use Cases

Conversational Issue Filing: Conducts a guided QA session to clarify user problems without requiring the user to write formal reports.
Context-Aware Documentation: Explores the codebase to ensure issues use correct domain language and describe behaviors rather than implementation details.
Intelligent Breakdown: Automatically determines if a report should be a single issue or a series of blocked sub-tasks to maximize development efficiency.

Quick Start

Initiate a qa session to discuss the recent issues you have encountered with the application.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I turn user feedback into GitHub issues?▼

You can convert user feedback into GitHub issues by running a guided QA session that clarifies the bug details, explores codebase context for accurate domain language, and generates structured, behavior-focused reports automatically.

Do I need GitHub CLI to automate issue tracking from bug reports?▼

Yes, GitHub CLI integration is required to programmatically create and manage issue tracking workflows, allowing the session to directly file the structured bug reports as durable issues in your repository.

What is the best way to file bug reports without writing formal documentation?▼

The best way is using conversational issue filing, a process where an interactive QA session clarifies the user's problem and captures the context, automatically translating informal feedback into high-quality, durable GitHub issues.

Can conversational QA sessions break down complex bug reports into sub-tasks?▼

Yes, intelligent breakdown functionality automatically determines if a report should be a single issue or a series of blocked sub-tasks, structuring the GitHub issues to maximize development efficiency.

How does context-aware documentation improve software testing issue reports?▼

Context-aware documentation improves issue reports by exploring the codebase to ensure they use correct domain language and describe actual behaviors rather than implementation details, increasing clarity for developers.

What are the limitations of converting conversational feedback into issue tracking workflows?▼

This approach relies entirely on GitHub CLI integration for programmatic creation and management, meaning it is limited to GitHub repositories and cannot directly file issues to other issue tracking platforms.