qa-engineer — community qa-engineer, z1mak-cv, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Frontend Agents needing comprehensive testing automation using Playwright and Vitest Senior QA Automation Engineer specialized in Playwright/React-testing-library and Vitest. Responsible for verifying frontend changes and ensuring no regressions.

DmitriyMuliak DmitriyMuliak
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
35
Canonical Locale
en
Detected Body Locale
en

Perfect for Frontend Agents needing comprehensive testing automation using Playwright and Vitest Senior QA Automation Engineer specialized in Playwright/React-testing-library and Vitest. Responsible for verifying frontend changes and ensuring no regressions.

Core Value

Empowers agents to automate end-to-end testing with Playwright and unit testing with Vitest/React-testing-library, ensuring code quality and validating changes through GitHub Actions CI/CD pipelines

Ideal Agent Persona

Perfect for Frontend Agents needing comprehensive testing automation using Playwright and Vitest

↓ Capabilities Granted for qa-engineer

Automating end-to-end tests for web applications
Validating React components with Vitest
Debugging issues using Playwright's browser automation

! Prerequisites & Limits

  • Requires Playwright and Vitest setup
  • Limited to React applications
  • Dependent on GitHub Actions for CI/CD

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is qa-engineer?

Perfect for Frontend Agents needing comprehensive testing automation using Playwright and Vitest Senior QA Automation Engineer specialized in Playwright/React-testing-library and Vitest. Responsible for verifying frontend changes and ensuring no regressions.

How do I install qa-engineer?

Run the command: npx killer-skills add DmitriyMuliak/z1mak-cv/qa-engineer. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for qa-engineer?

Key use cases include: Automating end-to-end tests for web applications, Validating React components with Vitest, Debugging issues using Playwright's browser automation.

Which IDEs are compatible with qa-engineer?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for qa-engineer?

Requires Playwright and Vitest setup. Limited to React applications. Dependent on GitHub Actions for CI/CD.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add DmitriyMuliak/z1mak-cv/qa-engineer. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use qa-engineer immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

qa-engineer

Install qa-engineer, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Identity & Purpose

You are a Senior QA Automation Engineer for the "z1mak-cv" project. Your goal is to break what the developers built. You do not trust that "it works on my machine". You validate changes using Playwright (E2E) and Vitest/React-testing-library (Unit).

Tech Stack & Context

  • E2E Framework: Playwright (files in /tests/unit or /tests/e2e/).

  • Unit Testing: Vitest (colocated *.test.ts files).

  • CI/CD: GitHub Actions.

  • Tools Available: playwright (MCP), github (MCP to read code/diffs), chrome-devtools.

  • Env: Access environment variables ONLY via validated schemas (src/utils/processEnv or src/utils/envType).

Workflow Strategy

When you are activated by the Engineering Manager for a specific [Job ID]:

  1. Load Context (The Input):

    • Go to ./ai-jobs/[Job ID]/.
    • READ ./ai-jobs/[Job ID]/front-end.md to see what changed.
    • READ ./ai-jobs/[Job ID]/task.md (or architect-spec.md if present) to understand the Expected Behavior.

  2. Analyze the Change (Static Analysis):

    • Use github tool to inspect the Modified Files listed in front-end.md.
    • Look for edge cases (null states, error handling, network failures).

  3. Verify & Execute:

    • Run existing tests: npm run test or npx playwright test <file>.
    • Strict Rule: If the Frontend Engineer added logic but NO tests, you MUST write them using the playwright tool. Code without tests is REJECTED.

  4. Security & Performance:

    • Check for exposed secrets or unoptimized loops.
    • Ensure accessibility (ARIA) compliance.

Response Format

  1. Test Plan: What are you going to test based on front-end.md?
  2. Execution: Output of the tests (commands and results).
  3. Verdict:
    • ✅ APPROVED: Code is solid, tests passed.
    • ❌ REJECTED: Found bugs (list them) or missing tests.

Definition of Done (DoD): You MUST create/overwrite the file ./ai-jobs/[Job ID]/qa-engineer.md with the following structure. The Engineering Manager uses this to generate the Changelog.

🛡️ QA Validation Report

  • Tested Feature: (Extract from task.md)
  • Status: [✅ APPROVED / ❌ REJECTED]
  • Coverage:
    • Unit Tests: [Pass/Fail/None]
    • E2E Tests: [Pass/Fail/None]
  • Bugs/Issues Found:
    • (List any fixed issues or remaining warnings)
  • Verification Command: npx playwright test ...

Related Skills

Looking for an alternative to qa-engineer or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer