evanflow-qa

Draft GitHub issue briefs from user-reported bugs through guided QA sessions.

417|18|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/evanklem/evanflow --skill evanflow-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evanflow-qa
Source: https://github.com/evanklem/evanflow/tree/main/skills/evanflow-qa
Command: npx skills add https://github.com/evanklem/evanflow --skill evanflow-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conversational bug discovery to draft an issue. Provides light listening, optional background exploration, and scope assessment, ensuring you ask before creating a GitHub issue and never auto-file. Use during QA sessions, triaging user-reported issues, or filing bugs.

Core Features & Use Cases

  • Light listening to gather user bug descriptions with minimal questions
  • Optional background exploration to understand code context without jumping to fixes
  • Scope assessment to decide if a single issue or multiple issues are needed
  • Draft the issue(s) and show them to the user before filing
  • Safe, human-in-the-loop filing with explicit permission

Quick Start

Initiate a QA session with a user-reported bug and draft the GitHub issue before filing.

Frequently Asked Questions about evanflow-qa

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

FAQPage Schema
How do I draft a GitHub issue from a user-reported bug?

Triage multiple bug reports through scope assessment to decide if they require separate issue drafts. The workflow guides you through discovery and scoping, then drafts each issue individually and shows them before filing anything on GitHub.

Can I automatically file GitHub issues from bug reports?

No, automatic filing is not supported. The workflow enforces human-in-the-loop decisions and requires explicit permission before creating or filing any GitHub issue, ensuring you review every drafted issue brief first.

What is QA triage for bug discovery and scoping?

QA triage is a conversational process that uses light listening to gather bug descriptions and optional background exploration to understand code context. It assesses scope to determine if a single issue or multiple issues are needed before drafting.

Do I need to provide code context when drafting an issue brief?

Providing code context is optional. The workflow uses light listening to gather user bug descriptions with minimal questions, but allows optional background exploration to understand the code context without jumping to fixes.