QA Test Case Generation
Use when generating manual QA test cases from requirements, BRDs, user stories, acceptance criteria, spreadsheets, live mockup/prototype URLs, uploaded mockups, screenshots, wireframes, or existing test case templates; especially when coverage, deduplication, traceability, validations, permissions, workflows, or edge cases matter.
Install
npx skills add saleem-daqa/qa-test-case-generation --skill qa-test-case-generationgit clone --depth 1 https://github.com/saleem-daqa/qa-test-case-generation.git /tmp/qa-test-case-generation
mkdir -p ~/.claude/skills
cp -r /tmp/qa-test-case-generation/. ~/.claude/skills/qa-test-case-generationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# QA Test Case Generation ## Overview Act as a senior manual QA engineer. Analyze requirements and optional mockups/templates, then produce professional, complete, practical, non-duplicated test cases that are ready for Excel, Google Sheets, or a test management tool. The output must be traceable to requirements, mockup elements, business rules, or logical QA risks. Do not invent unrealistic requirements; document assumptions and clarifications when information is missing. ## Resources Use these files as needed: - `assets/default-test-case-template.md` - default table format when no user template is provided. - `references/qa-coverage-checklist.md` - broad QA coverage checklist. - `references/boundary-edge-case-checklist.md` - validation, boundary, and edge-case prompts. - `references/deduplication-rules.md` - rules for removing repeated or overlapping cases. - `references/live-mockup-url-review.md` - detailed checklist for inspecting live mockup or prototype URLs. - `examples/sample-output.md` - compact example of final output style. ## Workflow ### Step 1: Intake Analysis Identify every provided input before generating test cases: - Required requirement source: requirements document, spreadsheet, BRD, user story, feature description, acceptance criteria, API spec, or ticket. - Optional live mockup/prototype URL. - Optional uploaded mockups, screenshots, wireframes, prototypes, or UI references. - Optional existing test case template.
Details
- Skill name
qa-test-case-generation- Repository
- saleem-daqa/qa-test-case-generation
- License
- MIT
- Repo updated
- 14 May 2026
FAQ
What does the QA Test Case Generation skill do?
Use when generating manual QA test cases from requirements, BRDs, user stories, acceptance criteria, spreadsheets, live mockup/prototype URLs, uploaded mockups, screenshots, wireframes, or existing test case templates; especially when coverage, deduplication, traceability, validations, permissions, workflows, or edge cases matter.
How do I install the QA Test Case Generation skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add saleem-daqa/qa-test-case-generation --skill qa-test-case-generation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is QA Test Case Generation popular?
It lives in saleem-daqa/qa-test-case-generation, which has 12 GitHub stars and 2 forks.
Related skills
Aftermath
14moah0911/aftermath
Post-failure recovery when something already broke: test suite went green to red, same error repeats after a fix, build or dependency resolution fails, a test is flaky, a merge conflicts, a destructive command is blocked, a forward edit is frozen, user says "you broke it", or the fix touched files outside scope. Stop, revert cheap damage, diagnose honestly, return to last-known-good. Supports lite/full/ultra, opt-in checkpoint autoRevert. Use ONLY for recovery after failure, not for planning new work.
Laravel Nova to Filament
15bkuhl/laravel-nova-to-filament-skill
Perform a complete, production-quality migration from Laravel Nova to Filament PHP v5. Covers field mapping, resources, actions, filters, lenses, metrics, dashboards, authorization, navigation, and testing with idiomatic Filament v5 patterns.
Does It Work
11TsakunovR/does-it-work
Проверка, что продукт реально работает, и защита его качества автотестами. Аудит работающего (в т.ч. навайбкоженного) приложения: найти баги, оценить готовность к проду, выдать баг-репорт с severity. Генерация тестовых фреймворков: API-тесты на Python (pytest + httpx + Pydantic + Allure) и Java (JUnit 5 + REST Assured), WEB/UI-тесты (Playwright, Selenium, Selenide, Page Object); конвертация OpenAPI/Postman/curl/HAR в тесты, негативные кейсы, контракты. Также стабилизация флакающих тестов и ревью качества тестов. Triggers: "проверь мой продукт/приложение", "найди баги", "навайбкодил", "можно ли
Ic Testing Notes
12wuyu25394-alt/sziit-speedcury-st2500-ate-skill
集成电路测试(ATE)知识库与实操手册,基于加速科技 ST2516/ST2500 测试平台与六个实训案例(CD4511 数字译码器、HK24C02 存储、LM358 运放、TPS73625 电源管理、HK32F031F4P6 MCU、ADC0832 数模混合),另含 74HC138、74HC595 扩展案例(3-8 译码器 / 8 位移位寄存器 + TMU 时序 + 虚拟 ATE)。当问题涉及 SMU/DPS/PPMU/BPMU/RVS/TMU/AWG/DGT/CBIT 等测试资源、开短路(OS)/漏电流(IIL/IIH)/VOH/VOL/IDD 等直流参数测试、Pattern 与 Timing 及 PinLevel 功能测试、FVMV/FVMI/FIMV/FIMI/FNMV 测量模式、ATE 工程文件(.job/.tmf/.sig/.grp/.res/.tim/.pat/Test.cpp)、或上述六款芯片的测试开发、限值设定与排错时使用。也适用于集成电路测试课程的复习、答疑、作业与实训。
Red Green Mode
11hidevinliu/red-green-mode
Autonomous test-fix loop: run an objective verifier (tests, type-check, lint, CI), fix what is red, re-run, and finish only when the verifier exit code is all green. Use when the user wants work driven to green without supervision, including long-run or parallel runs (红绿灯模式 / 跑到全绿 / 把 CI 修到全绿). Not for subjective work with no verifier or one-shot edits; use test-driven-development to write tests and systematic-debugging to root-cause one bug.
Cloakbrowser
14OctavianTocan/cloakbrowser-skill
Stealth Chromium browser automation that bypasses bot detection. Use this skill whenever the user wants to scrape, screenshot, PDF, or automate a site that blocks normal headless browsers — Cloudflare Turnstile, reCAPTCHA v3, FingerprintJS, ShieldSquare, BrowserScan, "Access Denied" responses, suspicious 403/429s on plain `curl`, or any site where Playwright/Puppeteer get caught. Also use when the user mentions CloakBrowser, stealth Chromium, anti-bot bypass, "headless detection", "real Chrome fingerprint", or wants a one-off "what does this page actually render" check. Prefer this skill over
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.