KS
Killer-Skills

qa-engineer — how to use qa-engineer how to use qa-engineer, qa-engineer setup guide, qa-engineer vs Cypress, qa-engineer install, what is qa-engineer, qa-engineer alternative, qa-engineer Playwright integration, qa-engineer Vitest setup, qa-engineer GitHub Actions pipeline

v1.0.0
GitHub

About this Skill

Perfect for Frontend Agents needing comprehensive testing automation using Playwright and Vitest qa-engineer is a skill that automates end-to-end and unit testing using Playwright and Vitest/React-testing-library for the z1mak-cv project.

Features

Utilizes Playwright for end-to-end testing in /tests/e2e/ directory
Employs Vitest and React-testing-library for unit testing in colocated *.test.ts files
Integrates with GitHub Actions for CI/CD pipeline automation
Leverages Playwright commands for test execution
Supports test validation using Vitest and React-testing-library assertions

# Core Topics

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

Quality Score

Top 5%
35
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add DmitriyMuliak/z1mak-cv/qa-engineer

Agent Capability Analysis

The qa-engineer MCP Server by DmitriyMuliak is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for how to use qa-engineer, qa-engineer setup guide, qa-engineer vs Cypress.

Ideal Agent Persona

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

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

Capabilities Granted for qa-engineer MCP Server

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
Project
SKILL.md
2.4 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

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 building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

widget-generator is an open-source AI agent skill for creating widget plugins that are injected into prompt feeds on prompts.chat. It supports two rendering modes: standard prompt widgets using default PromptCard styling and custom render widgets built as full React components.

149.6k
0
Design

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication