Skip to main content Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill cicd-pipeline-qe-orchestratorEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Ruflo is a multi-agent orchestration platform for AI coding agents (Claude Code, Cursor, Codex, Copilot, Gemini, Amp, +12 more). Use this skill when the user wants to (1) install/init ruflo in a project, (2) run multi-agent swarms with hierarchical coordination, (3) use ruflo's 314+ MCP tools for memory, routing, hooks, sub-agents, or workflows, (4) check ruflo status/version/doctor health, or (5) discover which of ruflo's 30+ plugins fits their task.
Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
Explorador de archivos
8 archivos name cicd-pipeline-qe-orchestrator description Orchestrate quality engineering across CI/CD pipeline phases. Use when designing test strategies, planning quality gates, or implementing shift-left/shift-right testing. category infrastructure priority critical tokenEstimate 1300 agents ["qe-fleet-commander","qe-test-generator","qe-test-executor","qe-coverage-analyzer","qe-quality-gate","qe-deployment-readiness"] implementation_status optimized optimization_version 1 last_optimized "2025-12-02T00:00:00.000Z" dependencies ["agentic-quality-engineering","shift-left-testing"] quick_reference_card true tags ["cicd","pipeline","orchestration","quality-gates","shift-left","shift-right","fleet"] trust_tier 3 validation {"schema_path":"schemas/output.json","validator_path":"scripts/validate-config.json","eval_path":"evals/cicd-pipeline-qe-orchestrator.yaml"}
CI/CD Pipeline QE Orchestrator
<default_to_action>
When orchestrating quality across CI/CD pipeline:
ANALYZE pipeline phases: commit, build, test, staging, production
SELECT optimal skills and agents for each phase
CONFIGURE quality gates with measurable thresholds
EXECUTE with parallel agent coordination
ADAPT strategy based on risk, complexity, and environment
Quick Phase Selection:
Commit (Shift-Left) → TDD, code review, unit tests
Build → Coverage analysis, mutation testing, flaky detection
Integration → API contracts, performance, security
Staging → Chaos testing, visual regression, accessibility
Production (Shift-Right) → Synthetic monitoring, RUM, compliance
Critical Success Factors:
Quality gates block bad deployments
Agents coordinate through memory namespaces
Adapt strategy based on risk level
</default_to_action>
Quick Reference Card
When to Use
Designing pipeline test strategies
Implementing quality gates
Coordinating multiple QE agents
Shift-left and shift-right testing
Phase-Agent Matrix
Phase Primary Agents Key Skills Commit qe-test-generator, qe-requirements-validator tdd-london-chicago, shift-left Build qe-test-executor, qe-coverage-analyzer, qe-flaky-test-hunter test-automation, mutation-testing Test qe-api-contract-validator, qe-performance-tester, qe-security-scanner api-testing, performance, security Staging qe-chaos-engineer, qe-visual-tester, qe-deployment-readiness chaos-engineering, accessibility Prod qe-production-intelligence, qe-quality-analyzer shift-right, compliance
Quality Gate Thresholds
Phase Metric Threshold Blocking Commit Unit coverage > 80% Yes Build All tests pass
Build Mutation score > 70% No
Test API contracts No breaking changes Yes
Test p95 response < 200ms Yes
Test Security critical 0 Yes
Staging Deployment readiness > 85% Yes
Fleet Configuration
Topology : hierarchicalMax Agents : 10 per phaseCoordination : aqe/* memory namespace
Pipeline Phases
Phase 1: Commit (Shift-Left) Goal: Catch defects early, ensure testability
qe-test-generator - Generate unit testsqe-requirements-validator - BDD scenarios, INVEST criteria Skills: shift-left-testing, tdd-london-chicago, code-review-quality
Task ("Generate Tests" , "Create unit tests for new methods" , "qe-test-generator" )
Task ("Validate Requirements" , "Check BDD scenarios" , "qe-requirements-validator" )
Gates: Unit coverage > 80%, Static analysis clean, Code review approved
Phase 2: Build Goal: Validate integration, ensure coverage
qe-test-executor - Run test suitesqe-coverage-analyzer - Coverage gaps (O(log n))qe-flaky-test-hunter - Detect/stabilize flaky testsqe-regression-risk-analyzer - Minimal regression suite Skills: test-automation-strategy, mutation-testing, regression-testing
Task ("Execute Tests" , "Run full suite, store in aqe/test-results/*" , "qe-test-executor" )
Task ("Coverage Analysis" , "Identify gaps" , "qe-coverage-analyzer" )
Task ("Flaky Detection" , "Analyze test history" , "qe-flaky-test-hunter" )
Gates: All tests pass, Coverage > 90% critical paths, No new flaky tests
Phase 3: Integration/Test Goal: Validate contracts, performance, security
qe-api-contract-validator - Breaking changes detectionqe-performance-tester - Load test critical pathsqe-security-scanner - SAST/DAST scansqe-test-data-architect - Realistic test data (10k+/sec) Skills: api-testing-patterns, performance-testing, security-testing
Task ("API Contracts" , "Validate for breaking changes" , "qe-api-contract-validator" )
Task ("Performance" , "Load test 1000 users" , "qe-performance-tester" )
Task ("Security" , "SAST/DAST scan" , "qe-security-scanner" )
Gates: No breaking API changes, p95 < 200ms, No critical vulnerabilities
Phase 4: Staging Goal: Validate production-like environment, resilience
qe-chaos-engineer - Fault injectionqe-visual-tester - Visual regressionqe-deployment-readiness - Risk assessment Skills: chaos-engineering-resilience, accessibility-testing, visual-testing
Task ("Chaos Testing" , "Controlled failure injection" , "qe-chaos-engineer" )
Task ("Visual Testing" , "Visual regression" , "qe-visual-tester" )
Task ("Deployment Check" , "Risk assessment" , "qe-deployment-readiness" )
Gates: Chaos tests pass, No visual regressions, Readiness > 85%
Phase 5: Production (Shift-Right) Goal: Monitor real usage, validate compliance
qe-production-intelligence - Incident → test scenariosqe-quality-analyzer - Quality metrics and trends Skills: shift-right-testing, compliance-testing
Task ("Production Intelligence" , "Convert incidents to tests" , "qe-production-intelligence" )
Task ("Quality Analysis" , "Production metrics" , "qe-quality-analyzer" )
Gates: Synthetic monitors pass, Error rate < 0.1%, Compliance validated
Complete Pipeline Example
Task ("TDD Generation" , "Generate tests for new features" , "qe-test-generator" )
Task ("Requirements" , "Validate BDD scenarios" , "qe-requirements-validator" )
Task ("Execute Tests" , "Full suite with coverage" , "qe-test-executor" )
Task ("Coverage" , "Analyze gaps" , "qe-coverage-analyzer" )
Task ("Flaky Hunt" , "Stabilize flaky tests" , "qe-flaky-test-hunter" )
Task ("API Contracts" , "Check breaking changes" , "qe-api-contract-validator" )
Task ("Performance" , "1000 user load test" , "qe-performance-tester" )
Task ("Security" , "SAST/DAST scans" , "qe-security-scanner" )
Task ("Chaos" , "Fault injection testing" , "qe-chaos-engineer" )
Task ("Visual" , "Visual regression" , "qe-visual-tester" )
Task ("Readiness" , "Deployment assessment" , "qe-deployment-readiness" )
Task ("Intelligence" , "Convert incidents" , "qe-production-intelligence" )
Task ("Quality Gate" , "Final validation" , "qe-quality-gate" )
Adaptive Strategy
By Risk Level Risk Strategy Agents Critical All phases, manual gates Full fleet High Automated gates, comprehensive 10+ agents Medium Smart selection, risk-based 5-8 agents Low Minimal regression, fast 2-3 agents
By Application Type Type Focus Skills Primary Agents API api-testing, contract, performance api-contract-validator, performance-tester Web UI visual-testing, accessibility visual-tester, accessibility Mobile mobile-testing, compatibility performance-tester, visual-tester Backend database-testing, security security-scanner, performance-tester
Agent Coordination Hints
Memory Namespace aqe/pipeline/
├── phase-results/* - Results from each phase
├── quality-gates/* - Gate validation results
├── orchestration-plan/* - Selected skills and agents
├── test-plan/generated - Test plans
├── coverage/gaps - Coverage analysis
├── security/findings - Security results
└── performance/results - Performance data
Fleet Orchestration Task ("Fleet Orchestration" ,
"Coordinate 10 agents across phases: commit (2), build (3), test (3), staging (2)" ,
"qe-fleet-commander" )
Blackboard Events Event Trigger Subscribers phase:commit:completeCommit phase done build agents coverage:gap:detectedGap found test-generator security:finding:criticalVulnerability quality-gate quality:gate:evaluatedGate decision fleet-commander
Quality Gate Configuration {
"commit" : {
"gates" : [
{ "metric" : "unit_coverage" , "threshold" : 80 , "blocking" : true } ,
{ "metric" : "static_analysis_critical" , "max" : 0 , "blocking" : true }
]
} ,
"build" : {
"gates" : [
{ "metric" : "all_tests_passed" , "threshold" : 100 , "blocking" : true } ,
{ "metric" : "mutation_score" , "threshold" : 70 , "blocking" : false }
]
} ,
"integration" : {
"gates" : [
{ "metric" : "api_breaking_changes" , "max" : 0 , "blocking" : true } ,
{ "metric" : "performance_p95_ms" , "threshold" : 200 , "blocking" : true } ,
{ "metric" : "security_critical" , "max" : 0 , "blocking" : true }
]
}
}
Troubleshooting Issue Cause Solution OOM during tests Running all tests in parallel Use batched execution Pipeline too slow Comprehensive testing every commit Smart test selection Gates always failing Thresholds too strict Analyze trends, adjust
Related Skills
Remember The CI/CD Pipeline QE Orchestrator provides:
Phase-based strategy with optimal skill/agent selectionQuality gates that block bad deploymentsAdaptive strategy based on risk and contextFull fleet coordination through memory namespaces With Agents: Use qe-fleet-commander for multi-agent orchestration. Coordinate through aqe/* memory namespace. Batch operations for efficiency.
