qa

Guide feature verification and automated checks across CLI, UI, and API surfaces.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software QA is often manual, repetitive, and error-prone. This skill guides users through comprehensive feature testing, providing a structured approach to verify behavior and catch regressions across workflows.

Core Features & Use Cases

  • Guided manual testing: walk through each feature interactively to validate expected behavior.
  • Auto mode: execute predefined test flows, run checks, and capture results without manual input.
  • Pre-flight mapping: analyze the project structure and test plan to ensure coverage before running tests.

Quick Start

Run /qa to begin guided manual testing or enable auto mode with /qa auto to run all tests automatically.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate feature testing workflows across CLI, UI, and API surfaces?

Automated feature testing workflows across CLI, UI, and API surfaces are executed by enabling auto mode to run predefined test flows, perform environment checks, and capture results without manual input. Playwright handles UI interactions.

Can I perform manual exploratory testing without writing automated scripts?

Manual exploratory testing is supported through guided interactive sessions that walk through each feature to validate expected behavior. This approach verifies functionality without requiring automated script creation.

Does this approach work with Playwright for UI testing automation?

Playwright is used for UI testing automation to interact with end-to-end workflows. The testing process applies Playwright-based interactions to verify behavior across UI surfaces during automated checks.

What is pre-flight mapping in software QA and how does it ensure test coverage?

Pre-flight mapping is the process of analyzing the project structure and test plan before running tests to ensure comprehensive coverage. This checks for pre-flight blockers and validates the environment setup.

How do I switch between manual and automated QA modes for projects of varying sizes?

Manual and automated QA modes are toggled based on project needs, satisfying requirements for modular test planning. Users can run guided manual checks or switch to auto mode to execute all tests automatically.

What are the limitations of automated end-to-end workflows for regression testing?

Automated end-to-end workflows for regression testing rely on predefined test flows and pre-flight checks to catch errors. Limitations include handling unexpected UI changes or environment blockers not mapped during the pre-flight analysis phase.