qa-investigate

Reproduce reported software defects and isolate root causes through evidence collection.

2|1|Updated May 27, 2025
One-click install
npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-investigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-investigate
Source: https://github.com/VirtoCommerce/vc-mcp-testing-module/tree/main/skills/qa-investigate
Command: npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps QA engineers investigate suspected bugs systematically by reproducing issues, isolating the failing layer, collecting evidence, and producing actionable root-cause findings.

Core Features & Use Cases

  • Structured Bug Investigation: Guides investigations through environment resolution, reproduction, layer isolation, evidence capture, root-cause analysis, and handoff.
  • Evidence-Based Diagnosis: Captures browser, network, console, trace, deployment, and source-code evidence to prevent unsupported bug reports.
  • Use Case: When a Virto Commerce checkout or storefront issue is reported, use this Skill to reproduce the problem, identify the responsible layer or repository, and prepare a developer-ready defect handoff.

Quick Start

Use the qa-investigate skill to investigate the reported checkout issue VCST-1234, collect evidence, determine the root cause, and prepare a bug report.

Frequently Asked Questions about qa-investigate

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

FAQPage Schema
How do I investigate a reported software bug and find its root cause?

Bug investigation involves reproducing reported issues, isolating the failing layer, and collecting browser, network, and trace evidence to determine a root cause and prepare a developer-ready defect handoff.

What's the best way to structure QA defect reporting for developer handoff?

Structured QA defect reporting for developer handoff requires capturing environment validation, browser automation artifacts, trace correlation, and source-code evidence to prevent unsupported bug reports and ensure reliable findings.

How do I reproduce a Virto Commerce storefront issue and isolate the failing layer?

To reproduce a Virto Commerce storefront issue and isolate the failing layer, perform environment resolution, execute browser automation, analyze API logs, and correlate traces to pinpoint the responsible repository.

What evidence do I need to capture during root cause analysis for a checkout bug?

During root cause analysis for a checkout bug, capture browser, network, console, trace, deployment, and source-code evidence to validate the environment and prevent unsupported defect reports.

Does this bug investigation approach work for API debugging and log analysis?

Yes, the bug investigation approach applies to API debugging and log analysis by guiding environment validation, artifact capture, trace correlation, and source investigation procedures to produce reliable bug findings.