From ordis-quality-engineering
Routes quality engineering queries to specialist reference sheets on E2E testing, performance testing, chaos engineering, test automation, flaky tests, test data management, and quality practices.
npx claudepluginhub tachyon-beep/skillpacks --plugin ordis-quality-engineeringThis skill uses the workspace's default tool permissions.
**Your entry point to quality engineering methodology.** This skill routes you to the right reference sheet for comprehensive quality engineering guidance.
api-testing-strategies.mdchaos-engineering-principles.mdcontract-testing.mddependency-scanning.mde2e-testing-strategies.mdflaky-test-prevention.mdfuzz-testing.mdintegration-testing-patterns.mdload-testing-patterns.mdmutation-testing.mdobservability-and-monitoring.mdperformance-testing-fundamentals.mdproperty-based-testing.mdquality-metrics-and-kpis.mdstatic-analysis-integration.mdtest-automation-architecture.mdtest-data-management.mdtest-isolation-fundamentals.mdtest-maintenance-patterns.mdtesting-in-production.mdCreates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Your entry point to quality engineering methodology. This skill routes you to the right reference sheet for comprehensive quality engineering guidance.
This is a meta-skill that:
You should use this skill: When facing testing challenges, quality automation, performance concerns, or reliability engineering problems.
Ad-Hoc Testing: Write tests → Hope they catch bugs → Fix when broken
Quality Engineering: Strategy → Architecture → Automation → Observability
Use quality-engineering when:
Don't use quality-engineering when:
IMPORTANT: All reference sheets are located in the SAME DIRECTORY as this SKILL.md file.
When this skill is loaded from:
skills/using-quality-engineering/SKILL.md
Reference sheets like flaky-test-prevention.md are at:
skills/using-quality-engineering/flaky-test-prevention.md
NOT at:
skills/flaky-test-prevention.md ← WRONG PATH
When you see a link like [flaky-test-prevention.md](flaky-test-prevention.md), read the file from the same directory as this SKILL.md.
When the user asks about quality engineering topics, load the appropriate reference sheet:
| User's Question Topic | Load Reference Sheet |
|---|---|
| Test Fundamentals & Isolation | |
| Test independence, idempotence, order-independence, isolation | test-isolation-fundamentals.md |
| API & Integration Testing | |
| REST/GraphQL API testing, request validation, API mocking | api-testing-strategies.md |
| Component integration, database testing, test containers | integration-testing-patterns.md |
| End-to-End & UI Testing | |
| End-to-end test design, E2E anti-patterns, browser automation | e2e-testing-strategies.md |
| Screenshot comparison, visual bugs, responsive testing | visual-regression-testing.md |
| Performance & Load Testing | |
| Load testing, benchmarking, performance regression | performance-testing-fundamentals.md |
| Stress testing, spike testing, soak testing, capacity planning | load-testing-patterns.md |
| Test Quality & Maintenance | |
| Test coverage, quality dashboards, CI/CD quality gates | quality-metrics-and-kpis.md |
| Test refactoring, page objects, reducing test debt | test-maintenance-patterns.md |
| Mutation testing, test effectiveness, mutation score | mutation-testing.md |
| Static Analysis & Security | |
| SAST tools, ESLint, Pylint, code quality gates | static-analysis-integration.md |
| Dependency scanning, Snyk, Dependabot, vulnerability management | dependency-scanning.md |
| Fuzzing, random inputs, security vulnerabilities | fuzz-testing.md |
| Advanced Testing Techniques | |
| Property-based testing, Hypothesis, fast-check, invariants | property-based-testing.md |
| Production Testing & Monitoring | |
| Feature flags, canary testing, dark launches, prod monitoring | testing-in-production.md |
| Metrics, tracing, alerting, quality signals | observability-and-monitoring.md |
| Fault injection, resilience testing, failure scenarios | chaos-engineering-principles.md |
| Test Infrastructure | |
| Test pyramid, CI/CD integration, test organization | test-automation-architecture.md |
| Fixtures, factories, seeding, test isolation, data pollution | test-data-management.md |
| Flaky tests, race conditions, timing issues, non-determinism | flaky-test-prevention.md |
| API contracts, schema validation, consumer-driven contracts | contract-testing.md |
Symptoms:
Reference Sheet Sequence:
Symptoms:
Reference Sheet Sequence:
Symptoms:
Reference Sheet Sequence:
Symptoms:
Reference Sheet Sequence:
Symptoms:
Reference Sheet Sequence:
Only answer directly (without loading) for:
User demands "just answer, don't route" is NOT an exception - still load the reference sheet. User asking to skip routing signals they need the specialist guidance even more.
After routing, load the appropriate reference sheet for detailed guidance: