qa-execution

Execute repository-wide QA gates across CLI, HTTP, and Web UI flows.

Updated May 15, 2026
One-click install
npx skills add https://github.com/JBonfim/skill-developer --skill qa-execution-jbonfim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-execution
Source: https://github.com/JBonfim/skill-developer/tree/main/.agents/skills/qa-execution
Command: npx skills add https://github.com/JBonfim/skill-developer --skill qa-execution-jbonfim

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents risky releases by executing a repository-wide QA gate like a real user, covering verification, build quality, tests, and end-to-end flows across CLI, HTTP, and (when available) browser interfaces.

Core Features & Use Cases

  • Repository QA contract discovery: Automatically discovers the project’s install, verify, lint, build, test, and start commands and records key CI/E2E and Web UI signals.
  • End-to-end scenario execution: Runs a baseline gate, then exercises changed and regression-critical workflows through the most public interfaces available.
  • Regression diagnosis and automated coverage updates: Reproduces failures, fixes root causes, updates the narrowest automated coverage (including E2E when supported), and reruns the full gate with evidence.
  • Web UI validation (optional): When a Web surface exists, uses the agent-browser companion skill to validate 3–5 critical user flows with screenshots.

Quick Start

Ask for a full QA run by providing a destination for artifacts: Run qa-execution with argument-hint to store all evidence under qa-output-path.

Frequently Asked Questions about qa-execution

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

FAQPage Schema
How do I run full-project QA validation before a risky release?

Full-project QA validation executes by discovering repository verification contracts, running build quality gates, and testing CLI, HTTP, and Web UI workflows to prevent risky releases. It systematically exercises regression-critical paths and produces evidence-backed verification reports.

What is automated regression diagnosis and how does it update E2E coverage?

Automated regression diagnosis reproduces test failures, identifies root causes, and updates the narrowest automated coverage including E2E tests. It then reruns the full verification gate with evidence to confirm the regression is resolved.

Does this QA execution tool support Web UI testing and browser automation?

Yes, when a Web surface exists, this QA execution tool optionally validates 3 to 5 critical user flows using browser automation. It captures screenshots as evidence to validate UI workflows during the regression gate.

Can I use this to validate branch changes and refactors?

Yes, you can use this to validate branch changes, release candidates, migrations, and refactors. It applies scope planning and regression follow-up by running a baseline gate and exercising changed workflows through the most public interfaces.

How do I store test artifacts and execution evidence from a QA run?

To store test artifacts and execution evidence, you initiate a full QA run by providing a destination artifact directory path. The execution manages this directory to systematically record scenario classifications, root-cause diagnoses, and final verification reports.

What are the limitations of automated QA for Web UI validation?

The limitation of automated QA for Web UI validation is that it only triggers when a browser surface exists and is limited to validating 3 to 5 critical user flows. It requires the agent-browser companion skill to execute the browser automation.