qa

Run automated QA checks against acceptance criteria, visual fidelity, and DS compliance.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill qa-scripsteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Scripsteam/scrips-stack/tree/main/qa
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill qa-scripsteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA ensures Scrips features meet acceptance criteria, visual fidelity, and DS compliance before release.

Core Features & Use Cases

  • Structured testing workflow: verifies against acceptance criteria, visual regressions, and DS compliance across staging or local dev environments.
  • Regression and risk mitigation: captures baseline visuals and checks for unintended changes, enabling quick remediation.
  • Collaborative validation: provides a clear QA report and actionable feedback for developers and product owners.

Quick Start

Start a QA cycle by specifying the target URL or feature scope to initiate automated checks.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run QA checks against staging URLs for feature acceptance criteria?

QA validation works by running automated checks against Jira-derived acceptance criteria, visual fidelity baselines, and DS compliance rules across your specified staging or local dev environments.

What is visual regression testing and how does it capture unintended UI changes?

Visual regression testing captures baseline visuals of your feature and compares them against current staging states to detect unintended changes, enabling quick remediation before release.

Can I verify staging features using Jira acceptance criteria automatically?

Yes, you can verify staging features automatically by using Jira-derived acceptance criteria when available, allowing the QA tool to structurally test if your features meet defined requirements.

Does QA testing work on both local dev servers and staging environments?

QA testing works on both staging URLs and local dev servers, allowing you to target different environments to validate features and check for visual regressions and DS compliance.

What is the best way to check DS compliance and visual fidelity before release?

The best way to check DS compliance and visual fidelity is to run a structured QA cycle that tests your feature against baseline visuals and design system rules to generate an actionable feedback report.

How do I start a QA cycle to validate a specific feature scope?

Start a QA cycle by specifying the target URL or defining the feature scope, which initiates the automated checks against acceptance criteria, visual regressions, and DS compliance.