qa

Files durable GitHub issues from conversational bug reports during interactive QA sessions.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill qa-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-extras/skills/qa
Command: npx skills add https://github.com/toderian/project_template --skill qa-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning informal bug reports from a QA session into well-structured, durable GitHub issues is tedious and often produces tickets that reference fragile file paths or lack reproduction steps. This Skill runs an interactive QA session where you describe problems conversationally while the agent explores the codebase for context and files clean, user-focused issues automatically. ## Core Features & Use Cases - Conversational bug intake: Describe problems in your own words with at most 2-3 short clarifying questions, no over-interviewing. - Background codebase exploration: Learns the project's domain language and expected behavior so issues read naturally without citing files or line numbers. - Smart issue breakdown: Splits multi-part reports into thin, independently fixable issues with honest blocking relationships, filed in dependency order via gh issue create. - Use Case: During manual testing you notice the form validation is wrong, the success message is missing, and the redirect is broken. The agent files three separate GitHub issues with reproduction steps and blocking relationships, then prints the URLs. ## Quick Start Start a QA session and describe the bugs you have found so the agent can file them as GitHub issues.

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 a conversational bug report?

Start a QA session and describe each problem in your own words. The agent asks at most 2-3 clarifying questions about expected behavior and reproduction steps, then files the issue with gh issue create and shares the URL.

How does the QA skill decide to split one report into multiple issues?

It breaks a report down when the fix spans independent areas, has separable concerns different people could handle in parallel, or involves distinct failure modes. Single-behavior defects stay as one issue.

Does the QA skill require the GitHub CLI?

Yes, issues are created with gh issue create, so the gh CLI must be installed and authenticated. The agent files issues directly without asking for review and prints all URLs afterward.

Why do the filed issues avoid file paths and line numbers?

Issues are written to be durable so they still make sense after major refactors. They describe behaviors in the project's domain language rather than citing code locations that quickly go stale.

Can the QA skill explore the codebase while I report bugs?

Yes, it runs a focused background exploration using the host runtime's mechanism, such as an Explore subagent or parallel grep sweep, to learn domain language and expected behavior without trying to find a fix.