skills.rest
afonsoft
afonsoftCOMMUNITY
Explore all skills by this author →
Website𝕏@afonsoftGitHub

qa-analyst

Plans, executes, and reports QA test cycles with bug tracking and root-cause analysis.

Updated Jul 21, 2026
Search Tags:#root cause analysis#qa#verification#bug report#regression#test cases#test planning
One-click install
npx skills add https://github.com/afonsoft/gamehub --skill qa-analyst-afonsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-analyst
Source: https://github.com/afonsoft/gamehub/tree/main/.claude/skills/qa-analyst
Command: npx skills add https://github.com/afonsoft/gamehub --skill qa-analyst-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It brings disciplined QA practice to AI-assisted development: instead of shipping untested code, it walks through requirements analysis, test planning, test case creation, execution, bug reporting, and root-cause analysis so defects are caught before they reach production. ## Core Features & Use Cases - Full QA Cycle: Six phases from requirements interrogation (ambiguities, gaps, missing acceptance criteria) through test planning, case creation, execution, bug reporting, and process improvement. - Structured Templates: Standardized test case, bug report, test plan, and RCA templates with severity/priority scales and traceability to SPEC requirements. - Verification Gate: A final build/type-check/lint/test/security/diff checklist that blocks PR readiness until all checks pass. - Use Case: After implementing a new feature in a .NET project, ask for a QA review to get a prioritized test plan, executable test cases mapped to acceptance criteria, and a verification report before opening the PR. ## Quick Start Ask the assistant to run a QA analysis on the feature you just implemented and produce a test plan with test cases before opening the pull request.

Frequently Asked Questions about qa-analyst

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

FAQPage Schema
How do I create a test plan for a new feature?▼

Define scope (what is and is not tested), pick a layer strategy across unit, integration, API, and E2E tests, set coverage targets, and prioritize risks by business impact. The skill generates this plan and stores it in docs/qa/test-plan-<feature>.md for large features.

How to write a good bug report with reproduction steps?▼

A good bug report has an objective title, minimal reproduction steps, expected versus observed results, evidence such as logs or screenshots, severity and priority ratings, and environment details. Use neutral factual language describing observable behavior, never blame.

What test coverage should a .NET project target?▼

The skill targets 80% line and branch coverage for .NET, 85% for Java, and 90% for Python, adjustable per project guardrails. It uses dotnet test with Coverlet or XPlat Code Coverage and reportgenerator for measurement.

When should I not use automated QA analysis?▼

Skip it when the only task is writing production code with no verification need, or when a human QA team has explicitly taken ownership. The skill is designed for verification phases, not initial implementation.

Why re-run regression tests after every bug fix?▼

A fix that breaks neighboring flows is not a fix. Re-running the failing case plus regression on adjacent flows confirms the change resolved the defect without introducing new ones, and fixed bugs should become automated regression tests.

Related Skills

Explore More Software Engineering Skills→
learnzdevelopmenthublearnzdevelopmenthub
1

dev-test

Generate test plans and placeholder stubs from acceptance criteria.

Community
Advanced
driftinglydriftingly
1

fix-github-issue

Create a feature branch, run local tests, and submit a pull request for GitHub issues using the gh CLI.

Community
Advanced
mguinadamguinada

refactor

Automate safe code refactoring with Red-Green-Refactor cycles and tests.

Community
Intermediate
mycelium-hqmycelium-hq
31

tdd-substrate

Guide red-green-refactor TDD cycles for TypeScript (Vitest) and Python (pytest) stacks.

Official
Advanced