qa-engineer

Orchestrates eight test schemes for PaasFabric with unified pre-check, execution, and root-cause escalation.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill qa-engineer-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/lfuuu/claude-rules/tree/main/shared-skills/roles/qa-engineer
Command: npx skills add https://github.com/lfuuu/claude-rules --skill qa-engineer-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running and diagnosing tests across the PaasFabric platform involves many environments (local, KVM servers, nested VMs, CI pipelines) and inconsistent procedures. This Skill unifies all testing into one QA orchestrator with a single API (pre-check → execute → post-check → report), so test runs are reproducible, failures are diagnosed by root cause, and bugs are escalated to the right engineering role instead of being masked with workarounds. ## Core Features & Use Cases - Eight unified test schemes: local (unit/lint), e2e on KVM/KVM2, CI diagnostics via GitHub CLI, nested KVM, K8s matrix, PostgreSQL matrix, VirtMan E2E, and production deploy — all sharing the same report format and artifact storage. - Mandatory pre-checks: verifies pf version consistency, git sync between local and server, pip editable installs, disk space, and Terraform locks before any run, stopping early on divergence. - Root-cause escalation table: maps failure symptoms (Python tracebacks, Ansible fails, Terraform drift, Nexus 503, flaky tests) to the responsible agent such as /platform-engineer, /devops, or /reliability-engineer. - Use Case: After pushing a feature branch, invoke the e2e scheme to monitor CI in parallel with KVM tests, receive a structured pass/fail report, and get an automatic escalation hint when a test fails. ## Quick Start Ask the agent to run the local test scheme with /qa-engineer local, or run the full E2E suite on the KVM server with /qa-engineer e2e kvm.

Frequently Asked Questions about qa-engineer

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

FAQPage Schema
How do I run E2E tests on a KVM server?

Invoke the e2e scheme with /qa-engineer e2e kvm or kvm2. It runs CI monitoring and KVM tests in parallel: git pull, pip editable install, unit and integration pytest suites, Terraform validation, and the E2E level 1.x group, producing a structured report.

How do I diagnose a failing GitHub Actions CI run?

Use the ci scheme with a PR number or run URL. It fetches failed job logs via gh run view --log-failed, classifies errors by category (shellcheck, ansible-lint, Terraform, unit tests, CI infra), and suggests fixes or reruns for infrastructure flakes.

What test schemes does the qa-engineer skill support?

Eight schemes share one API: local, e2e, ci, nested, k8s-matrix, pg-matrix, virtman, and deploy. Schemes can be chained with plus syntax, for example local+e2e, stopping at the first failure.

Why does pip fail with command not found over SSH on KVM servers?

Non-interactive SSH sessions do not load shell profiles, so $HOME/.local/bin is missing from PATH. Prefix every remote pip, pf, or pytest command with export PATH=$HOME/.local/bin:/usr/local/bin:$PATH.

What happens when a test failure is caused by a product bug?

The skill never writes code or applies workarounds. It investigates the root cause, then escalates to the responsible role: /platform-engineer for code or Ansible bugs, /devops for packaging issues, /reliability-engineer for VM infrastructure problems.

Can I run Kubernetes or PostgreSQL deployment matrices?

Yes. The k8s-matrix scheme covers single, multi-node, and HA clusters across Ubuntu and ALT OS versions, while pg-matrix covers single and HA (async/sync) PostgreSQL 15-17 across three operating systems, each with defined validation checks.