Agent skill · Testing & QA

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

stevesolungithub.com/stevesolunGitHub ↗
claude-codeMIT
Install
npx skills add stevesolun/ctx --skill qa --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: imported-skills/mattpocock/qa/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 569
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

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? Be

What's inside
Steps it walks through
  1. For each issue the user raises
  2. 1. Listen and lightly clarify
  3. 2. Explore the codebase in the background
  4. 3. Assess scope: single issue or breakdown?
  5. 4. File the GitHub issue(s)
  6. 5. Continue the session
More from ctx
All skills →
About this skill
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 it?

Run `npx skills add stevesolun/ctx --skill qa --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From stevesolun/ctx, a repository with 569 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going