qa-engineer

Enforce test pyramid strategies across unit, integration, API, E2E, and performance layers.

Updated Aug 27, 2026

Search Tags:#automation #testing #performance #qa #quality-assurance #test-pyramid #software-testing

Ready to run

npx skills add https://github.com/phishkatlabs/phishkat-crew --skill qa-engineer-phishkatlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/phishkatlabs/phishkat-crew/tree/main/qa-engineer
Command: npx skills add https://github.com/phishkatlabs/phishkat-crew --skill qa-engineer-phishkatlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA architects enforce comprehensive test strategies across the full test pyramid, catching anti-patterns and validating performance contracts to prevent late-stage bugs.

Core Features & Use Cases

Test pyramid guidance: design and enforce unit, integration, and end-to-end testing balance with guardrails.
Quality contracts: define and verify testing requirements, coverage thresholds, and performance SLAs.
Use Case: when shipping a new feature, create a tailored QA plan with tests, metrics, and release gates.

Quick Start

Define a complete QA strategy for a feature that covers unit, integration, API, and performance tests.

Frequently Asked Questions about qa-engineer

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

FAQPage Schema

How do I design a test strategy that balances unit, integration, and end-to-end tests?▼

A robust test strategy balances the full test pyramid by enforcing testing contracts and coverage thresholds across unit, integration, API, and end-to-end layers. This approach prevents late-stage bugs by guiding QA planning with guardrails against anti-patterns.

What's the best way to enforce quality contracts and coverage thresholds for feature development?▼

Enforce quality contracts by defining and verifying strict testing requirements and coverage thresholds for feature development. This establishes clear release gates and performance SLAs, ensuring performance-sensitive workflows meet validation criteria before deployment.

How do I create a QA plan that includes performance validation and API testing?▼

Create a tailored QA plan by defining testing requirements across API and performance test layers. This enforces performance validation and API testing contracts, catching anti-patterns early and validating performance-sensitive workflows for new features.

When do I need to define testing contracts for integration points and performance-sensitive workflows?▼

Define testing contracts for integration points and performance-sensitive workflows when shipping new features across software projects. This enforces quality contracts and performance SLAs, preventing late-stage bugs and ensuring robust end-to-end functionality.

Why does my test strategy fail to catch late-stage bugs in performance-sensitive workflows?▼

Test strategies fail to catch late-stage bugs when they lack enforced testing contracts and performance validation across the full test pyramid. Avoiding anti-patterns and verifying performance SLAs across all test layers prevents these critical failures.

Can I use this test pyramid guidance to establish release gates for software projects and teams?▼

Yes, you can establish release gates for software projects by enforcing quality contracts and coverage thresholds. This guides QA planning across teams, ensuring features pass performance validation and anti-pattern avoidance checks before release.