Agent skill · operations · aiskillstore
qa
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
Why this skill is useful
Adds a structured process for filing GitHub issues based on user-reported bugs, which the AI wouldn't reliably generate on its own.
What it needs
Requires github account access. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
QA Session Run an interactive QA session. The user describes problems they're encountering. You clarify, explore the codebase for context, and file GitHub issues that are durable, user-focused, and use the project's domain language. For each issue the user raises 1. Listen and lightly clarify Let the user describe the problem in their own words. Ask at most 2-3 short clarifying questions focused on: What they expected vs what actually happened Steps to reproduce (if not obvious) Whether it's consistent or intermittent Do NOT over-interview. If the description is clear enough to file, move on. 2. Explore the codebase in the background While talking to the user, kick off an Agent (subagenttype=Explore) in the background to understand the relevant area. The goal is NOT to find a fix — it's to: Learn the domain language used in that area (check UBIQUITOUSLANGUAGE.md) Understand what the feature is supposed to do Identify the user-facing behavior boundary This context helps you write a better issue — but the issue itself should NOT reference specific files, line numbers, or internal implementation details. 3. Assess scope: single issue or breakdown? Before filing, decide whether this is a single issue or needs to be broken down into multiple issues. Break down when: The fix spans multiple independent areas (e.g. "the form validation is wrong AND the success message is missing AND the redirect is broken") There are clearly separable concerns that different people could work on in parallel The user describes something that has multiple distinct failure modes or symptoms Keep as a single issue when: It's one behavior that's wrong in one place The symptoms are all caused by the same root behavior 4. File the GitHub issue(s) Create issues with gh issue create. Do NOT ask the user to review first — just file and share URLs. Issues must be durable — they should still make sense after major refactors. Write from the user's perspective. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/qa