skills.rest
Uncodier
UncodierCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

makinari-rol-qa

Automate QA validation by declaring E2E scenarios and triaging runtime signals against requirement contracts.

1|Updated May 8, 2025
Search Tags:#automation#e2e#qa#scenarios#gate#test-id
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-rol-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: makinari-rol-qa
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-rol-qa
Command: npx skills add https://github.com/Uncodier/API --skill makinari-rol-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA is often an afterthought; this skill enforces a structured, declarative approach to validating frontend and backend work against requirement contracts, reducing risk before delivery.

Core Features & Use Cases

  • Declarative E2E scenarios authored against requirement contracts.
  • Gate-signal triage across runtime, API, and visual checks, with documented acceptance criteria.
  • Generates and maintains QA artifacts under .qa/scenarios and qa_results.json for audit and CI workflows.

Quick Start

Create a new scenario JSON under .qa/scenarios describing a concrete journey and run the QA workflow to validate the gate.

Frequently Asked Questions about makinari-rol-qa

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

FAQPage Schema
How do I automate E2E scenarios against a requirement contract for gated deployments?▼

You automate E2E scenarios by authoring declarative JSON files under .qa/scenarios that define deterministic journeys, form interactions, and accessibility checks using a strict test-id contract to validate frontend-backend gated deployments.

What is declarative QA validation and how does it triage runtime signals?▼

Declarative QA validation defines expected behavior in scenario files rather than imperative code, triaging runtime, API, and visual signals against acceptance criteria to enforce deterministic E2E outcomes before delivery.

How do I generate QA artifacts for CI workflows and audit trails?▼

You generate QA artifacts by running the validation workflow, which automatically creates and maintains qa_results.json files under the .qa/scenarios directory to provide auditable outcomes for CI pipelines.

Can I enforce a strict test-id contract for UI navigation and form interactions?▼

Yes, you can enforce a strict test-id contract for UI navigation and form interactions by applying it within your declarative E2E scenarios to ensure deterministic frontend element targeting during gate-signal triage.

What's the best way to structure seed-based QA scenarios for accessibility checks?▼

The best way to structure seed-based QA scenarios is to author them as declarative JSON files under .qa/scenarios, explicitly defining accessibility checks and acceptance criteria within a deterministic journey structure.

Do I need external dependencies to run declarative E2E scenarios for frontend and backend validation?▼

No external dependencies are required; you only need to create a scenario JSON under .qa/scenarios describing a concrete journey and run the QA workflow to validate the gate against your requirement contract.

Related Skills

Explore More Software Engineering Skills→
wukangcheng2944wukangcheng2944

test-cases

Transform PRDs and user requirements into structured Markdown test cases.

Community
Advanced
DRMacIverDRMacIver
18

Working on GitHub Issues

Guide GitHub issue triage, acceptance criteria, and referencing commits.

Community
Intermediate
distribucionesfayosmoreno-sysdistribucionesfayosmoreno-sys

ui-visual-validator

Validate UI modifications for visual regression, compliance, and accessibility.

Community
Advanced
haidonglethqbhaidonglethqb

ck:test

Automate unit, integration, e2e, and UI tests with coverage analysis.

Community
Advanced