qa

Convert user-reported bugs into domain-language GitHub issues after review.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/amodelandme/skill-tree-dotnet --skill qa-amodelandme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/amodelandme/skill-tree-dotnet/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/amodelandme/skill-tree-dotnet --skill qa-amodelandme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run interactive QA sessions where users describe bugs in plain language. The agent clarifies context, drafts issues using domain-language templates, and files them after user review.

Core Features & Use Cases

  • Clarify user-reported issues with at most 2-3 focused questions.
  • Draft durable, domain-language GitHub issues using templates from REFERENCE.md.
  • Generate chore files under chores/ after user approval and in dependency order.

Quick Start

Describe a bug in plain language and approve the drafted issues to file them.

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 QA session?

Filing GitHub issues from a QA session involves describing bugs conversationally; the agent then asks up to 3 clarifying questions, drafts issues using domain-language templates, and writes files after approval.

What is the process for converting plain language bug reports into domain-language issues?

The process maps plain language bug descriptions to domain-language issue templates by asking focused clarifying questions, drafting the issue, and writing it to chores/<id>.md upon approval.

Do I need a reference template file to draft issues using domain language?

Yes, drafting issues using domain language requires templates defined in a REFERENCE.md file, which the agent uses to structure user-reported bugs into durable GitHub issues.

Can I report bugs conversationally and generate chore files in dependency order?

Yes, reporting bugs conversationally generates chore files under chores/<id>.md in dependency order, but only after you review and approve the drafted domain-language issues.

What are the limitations of interactive QA for issue drafting?

Limitations of interactive QA for issue drafting include asking at most 2-3 focused clarifying questions, restricting sessions to plain language input, and requiring a REFERENCE.md file for templates.