Agentic Quality Engineering Fleet
What AQE Does For You
- Generates comprehensive tests automatically — unit, integration, property-based, and BDD scenarios for your codebase with framework-specific output (Jest, Vitest, Playwright, Cypress, pytest, JUnit, Go, Rust, Swift, Flutter, and more)
- Finds coverage gaps and prioritizes what to test — risk-weighted analysis identifies the most impactful untested code paths
- Detects and fixes flaky tests — ML-powered detection with root cause analysis and stabilization recommendations
- Learns your codebase patterns over time — remembered patterns are reused across sessions and projects, improving with every interaction
- Coordinates 60 specialized QE agents — from test generation to security scanning to chaos engineering, orchestrated by a central coordinator
- Reduces AI costs with intelligent routing — automatically routes tasks to the right model tier (fast/cheap for simple tasks, powerful for complex ones)
- Works with your existing tools — integrates with 11 coding agent platforms and your existing CI/CD pipeline
Quick Start
# Install
npm install -g agentic-qe
# Initialize your project (auto-detects tech stack, configures MCP)
cd your-project && aqe init --auto
# That's it — MCP tools are available immediately in Claude Code
# For other clients: aqe-mcp
After init, your coding agent can use AQE tools directly. For example in Claude Code:
"Generate tests for src/services/UserService.ts with 90% coverage target"
"Find coverage gaps in src/ and prioritize by risk"
"Run security scan on the authentication module"
"Analyze why tests in auth/ are flaky and suggest fixes"
Claude Code Plugin (Alternative Install)
If you only need a slim, scoped fleet inside Claude Code — without the full aqe init setup — install the agentic-qe-fleet plugin. It bundles 11 specialized QE agents, 9 slash commands, 9 skills, and auto-registers the MCP server.
Install from a local checkout
git clone https://github.com/proffesor-for-testing/agentic-qe.git
claude --plugin-dir ./agentic-qe/plugins/agentic-qe-fleet
Install from the marketplace
In any Claude Code session:
/plugin marketplace add proffesor-for-testing/agentic-qe
/plugin install agentic-qe-fleet
What you get
| Asset | Count | Notes |
|---|
| Agents (Task tool) | 11 | Model-routed: 6 on Opus (heavy reasoning), 5 on Sonnet (focused execution) |
| Slash commands | 9 | /aqe-analyze, /aqe-execute, /aqe-generate, /aqe-optimize, /aqe-chaos, /aqe-fleet-status, /aqe-report, /aqe-benchmark, /aqe-costs |
| Skills | 9 | All trust-tier 2 or 3 (validated/verified). Tier-1 untested skills excluded per policy. |
| MCP server | 1 | Auto-registers via npx -y agentic-qe@latest mcp — no separate claude mcp add |
Bundled agents: qe-test-architect, qe-coverage-specialist, qe-flaky-hunter, qe-chaos-engineer, qe-fleet-commander, qe-quality-gate, qe-security-scanner, qe-performance-tester, qe-regression-analyzer, qe-tdd-specialist, qe-requirements-validator.
Bundled skills: qe-test-generation, qe-coverage-analysis, qe-test-execution, qe-chaos-resilience, qe-quality-assessment, chaos-engineering-resilience, mutation-testing, risk-based-testing, tdd-london-chicago.
Use it
After loading the plugin, the slash commands and agents are available immediately:
/aqe-fleet-status # health and metrics
/aqe-generate src/services/Auth.ts
/aqe-analyze src/ # coverage gap analysis
Or invoke an agent through the Task tool:
"Use qe-test-architect to generate tests for src/services/PaymentService.ts"
"Use qe-flaky-hunter to find and stabilize flaky tests in tests/integration/"
"Use qe-chaos-engineer to inject network partitions into the order workflow"
Plugin vs aqe init — which to use?
