skills.rest
MediSolveAIDev
MediSolveAIDevOFFICIAL
Explore all skills by this author →
GitHub

review-qa

Identify missing edge cases and feasibility gaps in QA scenario and test case reviews.

Updated Feb 11, 2026
Search Tags:#qa#feasibility#review#edge-cases#scenario#tc
One-click install
npx skills add https://github.com/MediSolveAIDev/QA-MEDI-PLUGIN --skill review-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-qa
Source: https://github.com/MediSolveAIDev/QA-MEDI-PLUGIN/tree/main/.claude/skills/review-qa
Command: npx skills add https://github.com/MediSolveAIDev/QA-MEDI-PLUGIN --skill review-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often miss edge cases and negative scenarios when reviewing scenarios and test cases. This skill provides a rigorous QA-focused review to uncover gaps before development proceeds.

Core Features & Use Cases

  • Phase-based reviews: Scenario review to identify edge cases and negative paths, followed by TC review for feasibility and error handling.
  • Parallel validation with Spec Reviewer: Works alongside Spec Reviewer to ensure coverage without duplication.
  • Actionable findings: Generates structured findings including edge cases, negative scenarios, and feasibility notes.

Quick Start

Provide the TC JSON file path and the scenario MD path to initiate the QA review.

Frequently Asked Questions about review-qa

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

FAQPage Schema
How do I find missing edge cases in test scenarios before development starts?▼

To find missing edge cases in test scenarios, apply a structured QA review process that identifies negative paths and feasibility gaps during scenario drafting. This cross-check generates a standardized report of findings and recommended actions for comprehensive coverage.

How do I validate test case feasibility and error handling?▼

Validating test case feasibility requires a dedicated review phase that checks TCs for error handling and practical execution gaps. This produces feasibility classifications and actionable recommendations to harden test cases before development proceeds.

What is the best way to review test cases for negative scenarios?▼

Reviewing test cases for negative scenarios is best handled through a phase-based QA cross-check that operates during TC validation. It systematically uncovers uncovered negative paths and edge cases, outputting a structured findings report.

Can I run QA test case reviews in parallel with spec validation?▼

Yes, you can run QA test case reviews in parallel with spec validation. The QA review operates alongside spec validation tools to ensure comprehensive coverage without duplication, focusing purely on edge cases and feasibility.

How do I start a QA review for scenarios and test cases?▼

To start a QA review for scenarios and test cases, provide the test case JSON file path and the scenario markdown path. This triggers the structured workflow, executing Phase 1-A scenario review and Phase 1-B TC review to produce a standardized report.

What limitations exist when cross-checking test cases for edge cases?▼

A key limitation when cross-checking test cases is that the review focuses strictly on QA scenarios and TC feasibility, meaning it requires existing draft scenarios and TC files to function and does not generate initial test cases from scratch.

Related Skills

Explore More Software Engineering Skills→
MediSolveAIDevMediSolveAIDev

write-tc

Convert narrative scenarios into structured test-case JSON files.

Official
Advanced
anthropicsanthropics
9.1k

gaps

Report open remediation gaps from gap-tracker.yaml and update their status.

Official
Intermediate
gotalabgotalab
3.6k

kiro-spec-batch

Generate feature specifications from roadmaps using dependency-aware parallel subagents.

Community
Advanced
fdshg693fdshg693

copilot-test-skill

Validate Copilot integration with a minimal YAML frontmatter Skill unit.

Community
Basic