qa

Run existing tests and generate Playwright e2e coverage for Jira acceptance criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA ensures a reviewer can confidently verify that a shipped or in-review change actually works as expected against the acceptance criteria, without turning QA into slow back-engineering.

Core Features & Use Cases

  • Reviewer-triggered QA pass: Run verification when someone is picking up a change, not as part of the main build pipeline.
  • Test-first verification: Executes the project’s existing tests relevant to the change, records pass/fail, and escalates failures as QA findings.
  • Playwright e2e generation (when missing): Generates Playwright end-to-end checks for acceptance criteria when no existing e2e coverage exists, then runs them and captures traces/screenshots.
  • Subtask-by-subtask QA: If the target Jira ticket has subtasks, QA them one at a time rather than treating the whole epic as a single pass.
  • Human-friendly sign-off workflow: Produces a qa.md pass/fail artifact, offers interactive qa.html for manual checks, and lists any reviewer-required steps that can’t be safely automated.

Quick Start

Run /casaflow:qa CAS-NNNN to verify the change against its acceptance criteria, generate e2e checks if needed, and produce qa.md with pass/fail results.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I verify a pull request against Jira acceptance criteria?

You can verify a pull request against Jira acceptance criteria by targeting the ticket ID, PR URL, or branch name. The Skill runs existing tests and generates Playwright e2e coverage when absent, producing a qa.md sign-off artifact.

Can I generate Playwright e2e tests during a reviewer workflow if coverage is missing?

Yes, Playwright e2e tests can be generated during a reviewer workflow when no existing coverage exists. The Skill creates end-to-end checks for the acceptance criteria, runs them, and captures traces and screenshots for verification.

How do I run sequential QA on Jira subtasks instead of the whole epic?

Sequential QA on Jira subtasks is supported by resolving the target Jira ticket ID. The Skill splits automated versus manual checks and executes test runs for each subtask individually rather than treating the epic as a single pass.

What is the best way to produce a human-friendly QA sign-off artifact for manual checks?

The best way to produce a human-friendly QA sign-off artifact is to generate the qa.md pass/fail file alongside an interactive qa.html. These artifacts record test execution results and list any reviewer-required manual steps that cannot be safely automated.

Does reviewer-triggered test execution escalate test failures as QA findings?

Yes, reviewer-triggered test execution escalates test failures as QA findings. The Skill executes the project's existing tests relevant to the shipped change, records pass or fail status, and logs any failures into the qa.md artifact for review.