qa-test-strategy

Analyze test coverage gaps, quality, and architecture for code changes.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/dev-gios/agent-teams-qa --skill qa-test-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-test-strategy
Source: https://github.com/dev-gios/agent-teams-qa/tree/main/skills/qa-test-strategy
Command: npx skills add https://github.com/dev-gios/agent-teams-qa --skill qa-test-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill identifies gaps in test coverage, pinpoints issues with test quality, and suggests improvements to your overall test strategy, ensuring your code is robustly tested without writing the tests themselves.

Core Features & Use Cases

  • Coverage Gap Analysis: Detects missing tests for new code paths, functions, and edge cases.
  • Test Quality Assessment: Evaluates test naming, structure, isolation, and identifies anti-patterns.
  • Scenario Identification: Recommends specific tests for happy paths, error cases, and boundary conditions.
  • Use Case: After a code change, this Skill can report that a critical authentication function lacks tests for error scenarios, providing specific examples of what needs to be covered.

Quick Start

Analyze the test strategy and coverage for the recently changed files in the current project.

Frequently Asked Questions about qa-test-strategy

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

FAQPage Schema
How do I identify test coverage gaps after making code changes?

Test quality assessment evaluates test naming, structure, and isolation to identify common testing anti-patterns. It pinpoints structural issues in existing suites and provides actionable recommendations to improve overall test architecture.

What is the best way to find missing edge cases in my test suite?

Finding missing edge cases involves analyzing code changes to recommend specific tests for happy paths, error scenarios, and boundary conditions. This scenario identification ensures robust coverage for critical functions without manually writing the tests.

Can I analyze test architecture for recently changed files only?

Yes, you can analyze test strategy and coverage specifically for recently changed files in your current project. This targeted approach evaluates test quality and detects anti-patterns directly within your modified code scope.

Does this approach generate actual test code for missing scenarios?

No, this approach does not generate test code. It analyzes test coverage gaps and architecture, providing actionable recommendations and specific examples of what needs coverage, leaving the actual test implementation to the developer.