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".

5 stars 2 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add GAGAA-HUE/ASHUO-claude-skills --skill qa
Manual install
git clone --depth 1 https://github.com/GAGAA-HUE/ASHUO-claude-skills.git /tmp/ASHUO-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ASHUO-claude-skills/qa ~/.claude/skills/qa

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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 (subagent_type=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 UBIQUITOUS_LANGUAGE.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")
Read the full skill on GitHub

Details

Skill name
qa
Path
qa/SKILL.md
Repo updated
3 November 2026

FAQ

What does the QA skill do?

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".

How do I install the QA skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add GAGAA-HUE/ASHUO-claude-skills --skill qa. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is QA popular?

It lives in GAGAA-HUE/ASHUO-claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Domain Modeling

5

GAGAA-HUE/ASHUO-claude-skills

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

AI, LLMs & AgentsIn 2 lists

Git Guardrails Claude Code

5

GAGAA-HUE/ASHUO-claude-skills

Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.

Git & Code ReviewIn 2 lists

Setup Pre Commit

5

GAGAA-HUE/ASHUO-claude-skills

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

Testing & QAIn 2 lists

Unit Test

1

moveju112/skill_verify

Use when the user directly requests efficiency-aware multi-angle unit tests or a test report after code changes. Triggers include "단위 테스트", "유닛테스트", "테스트 돌려", "다방면 테스트", "테스트 문서 정리", and the English equivalents "unit test", "run the tests", "multi-angle tests", "write up the test results", and "/unit-test". Codex or Claude runs tests locally without calling another LLM, avoids duplicate full-suite gates, and writes a focused report to the project's test directory. Not for E2E, external DB/network checks, runtime verification, or performance benchmarks.

Testing & QAIn 1 list

Migrate to Shoehorn

5

GAGAA-HUE/ASHUO-claude-skills

Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

Testing & QA

Audit Feature Gates

5

TalonT-Org/AutoSkillit

Audit feature flag isolation — traces import chains, runtime gates, tool/skill tag coverage, UI surfaces, and test markers to detect leakage and miswiring.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.