qa

Convert user-reported bugs into actionable GitHub issues with codebase context.

Updated Apr 28, 2026

Search Tags:#qa #conversation #triage #github-issues #bug-report #codebase-exploration #issue-writing

Ready to run

npx skills add https://github.com/rnaarla/agent_skills --skill qa-rnaarla

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides interactive QA sessions that convert user-reported bugs into clear, actionable GitHub issues by exploring the codebase for context and using the project domain language.

Core Features & Use Cases

Interactive questioning to clarify bug symptoms, reproduce steps, and impact.
In-context codebase exploration to surface domain terms and relevant context.
Durable issue drafting that uses project terminology and logical acceptance criteria.

Quick Start

Describe the bug in plain terms and start an interactive QA session with the agent.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I convert a bug report into a structured GitHub issue?▼

You can draft actionable GitHub issues by describing the bug in plain terms; the skill guides an interactive session to clarify impact, explores the repository for domain context, and formats the final issue.

How does codebase exploration improve issue triage and writing?▼

Codebase exploration during issue triage surfaces relevant domain terms and project context, ensuring the drafted GitHub issue uses accurate terminology and logical acceptance criteria instead of generic descriptions.

Can I use this skill to triage user-reported bugs without writing manual reproduction steps?▼

Yes, you can triage user-reported bugs by starting an interactive QA session where the agent questions you to extract reproduction steps and impact, automatically generating the structured issue content.

What is the best way to ensure my GitHub issues use the correct project domain language?▼

The best way to ensure GitHub issues use correct project domain language is leveraging a skill that explores the repository context, automatically surfacing and applying your project's specific terminology to the final issue draft.

Do I need to provide codebase access for the agent to write durable bug reports?▼

Providing codebase access allows the agent to optionally explore the repository for context, which is necessary to accurately translate descriptive bug reports into actionable GitHub issues using your project's domain language.