qa

Convert user-reported problems into structured GitHub issues with reproduction steps.

5|2|Updated Nov 17, 2025

Search Tags:#workflow #github #qa #interactive #exploration #issues #bug

Ready to run

npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill qa-outlinedriven

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/qa
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill qa-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of reporting software issues discovered in plain language, bridging gaps between users and developers by ensuring every problem results in a clear, trackable GitHub issue.

Core Features & Use Cases

Interactive QA session: you gather user problem statements with minimal clarifications.
Background exploration: simultaneously learn domain language and define the issue scope without interrupting user flow.
Durable issue creation: generate well-structured GitHub issues that survive refactors and provide reproduction steps.

Quick Start

Describe the problem in plain language to start an interactive QA session.

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 found during ad-hoc testing as a durable GitHub issue?▼

You can report a bug as a durable GitHub issue by describing the problem in plain language to start an interactive QA session that clarifies scope, maps domain language, and generates structured issues with reproduction steps.

Can I use plain language to file GitHub issues without writing markdown manually?▼

Yes, you can file GitHub issues using plain language without manual markdown by entering an interactive QA session that captures your problem statement and converts it into a structured, durable issue.

What is the best way to ensure GitHub bug reports survive code refactors?▼

The best way to ensure GitHub bug reports survive code refactors is using durable issue templates that map domain language and define reproduction steps, maintaining context despite structural codebase changes.

Does this interactive QA workflow support both web and CLI bug reporting contexts?▼

Yes, this interactive QA workflow supports both web and CLI bug reporting contexts, applying ad-hoc user-reported problem statements to guide minimal clarifications and parallel background exploration for issue creation.

What should I do if my bug report lacks clear reproduction steps for GitHub?▼

If your bug report lacks reproduction steps for GitHub, start an interactive QA session that gathers minimal clarifications from your plain language statement to define issue scope and generate structured reproduction steps.