Skip to main content
subagent CX Codex

qa-expert · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install

qa-expert plans risk-based test strategies, acceptance criteria coverage, and release gating signals without checklist theater.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/qa-expert.toml
Open on GitHub

What qa-expert does

The subagent maps changed boundaries and potential failure surfaces across new features or releases. Rather than pushing full test passes for minor updates, it prioritizes the smallest intervention that cuts user-facing risk and keeps delivery moving.

Configured with the gpt-5.6-sol model, the agent validates a normal path, a failure path, and an integration boundary. It strictly avoids exhaustive testing mandates on low-risk scoped diffs unless requested.

Outputs detail the analyzed scope, confirmed findings versus hypotheses, suggested minimal fixes, and residual risks with concrete follow-up steps.

What it helps with

  • map critical failure surfaces in modified codebases
  • build acceptance test plans for positive and negative paths
  • define go/no-go gating criteria for upcoming releases
  • outline fixture and test data strategies for repeatable checks

Example prompts for the agent

  • Review the diff in this branch and identify boundary failure risks
  • Generate acceptance test scenarios for the new checkout flow
  • Assess release risks and specify gating criteria for deployment

How to install qa-expert

Manually: put the files in place

.codex/agents/qa-expert.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about qa-expert

How do I install qa-expert in Codex?

Add the subagent configuration file at .codex/agents/qa-expert.toml in your repository.

What does qa-expert do?

It evaluates code changes to build an evidence-driven test strategy focused on high-risk failure points and acceptance scenarios.

Which model powers qa-expert?

The subagent runs on gpt-5.6-sol as defined in its frontmatter configuration.

Source text

qa-expert.toml · MIT
# qa-expert

Use when a task needs test strategy, acceptance coverage planning, or risk-based QA guidance for a feature or release.

Own quality assurance planning work as evidence-driven quality and risk reduction, not checklist theater.

Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.

Working mode:
1. Map the changed or affected behavior boundary and likely failure surface.
2. Separate confirmed evidence from hypotheses before recommending action.
3. Implement or recommend the minimal intervention with highest risk reduction.
4. Validate one normal path, one failure path, and one integration edge where possible.

Focus on:
- risk-based test scope aligned with user impact and change complexity
- acceptance criteria coverage across positive, negative, and boundary scenarios
- integration points likely to regress with current change set
- non-functional checks (reliability, performance, accessibility, security) where relevant
- test data/fixture strategy needed for reliable repeatable execution
- release gating criteria and go/no-go decision signals
- clear handoff of high-priority test actions to implementation teams

Quality checks:
- verify test plan explicitly maps each critical risk to at least one validation path
- confirm missing automation or manual checks are prioritized by impact
- check coverage gaps that could allow silent regressions into release
- ensure recommendations are feasible within release timeline constraints
- call out environment dependencies needed for full QA confidence

Return:
- exact scope analyzed (feature path, component, service, or diff area)
- key finding(s) or defect/risk hypothesis with supporting evidence
- smallest recommended fix/mitigation and expected risk reduction
- what was validated and what still needs runtime/environment verification
- residual risk, priority, and concrete follow-up actions

Do not treat exhaustive testing as mandatory for low-risk scoped changes unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Testing and QA →

qa-expert by other authors comes first.

qa-expert VoltAgent Community qa-expert plans test strategies, analyzes coverage gaps, and tracks quality metrics across development lifecycles in Claude Code. CX Codex 980installs qa-expert qdhenry qa-expert — a subagent for designing test strategies, executing comprehensive tests, tracking defects, and assessing product quality. Helps identify issues early, build confidence in releases, and deliver data-driven quality reports. CX Codex ★ 1,357repo stars testing-strategy official anthropics testing-strategy is a Claude Code skill that designs test strategies and plans for components. It triggers on questions like how should we test or what tests do we need. CX Codex +1 6,800installs test-strategy kindlmann test-strategy turns a discovery interview into a QA strategy document covering test levels, entry and exit criteria, and quality KPIs. Useful when you need a direction, not a sprint plan. CX Codex +1 1,900installs risk-based-testing kindlmann risk-based-testing builds a risk matrix scored by business impact and probability, runs failure mode analysis on the top items, and maps test coverage to risk zones. Run it before test-strategy. CX Codex +1 1,800installs ui-ux-tester VoltAgent Community ui-ux-tester — a subagent that walks documented user flows in a browser or on the desktop and returns a defect report with visual proof. CX Codex ★ 26,718repo stars surgeon-reviewer VoltAgent Community surgeon-reviewer is a Claude Code subagent that reviews code changes for critical bugs, cost leaks, and structural risks, then gives a clear release verdict. CX Codex ★ 26,718repo stars testing-strategies akillness The testing-strategies skill turns unclear test policy into a focused validation brief. Use it to choose the gate, risk level, and evidence a change needs. CX Codex +1 370installs

From the same set176

The whole set →
ui-ux-tester ui-ux-tester — a subagent that tests your interface as a frustrated user: walks every documented flow end to end, catches micro-interaction bugs, validates error states and accessibility, produces a severity-ranked defect report. CX Codex ★ 6,505repo stars test-automator test-automator — a subagent for writing and improving automated tests. Focuses on high-risk behavior, minimal interventions, and defects that recur. CX Codex ★ 6,505repo stars security-auditor security-auditor is a Codex subagent that examines code, authentication flows, and infrastructure settings for security risks. It joins focused security review tasks. CX Codex ★ 6,505repo stars reviewer reviewer is a Codex subagent for PR-style checks of correctness, security, regressions, and test gaps. It joins tasks that call for a focused code review. CX Codex ★ 6,505repo stars powershell-security-hardening The powershell-security-hardening subagent reviews PowerShell safety, privileged automation, execution controls, and Windows security posture. Use it when a change needs evidence-backed hardening. CX Codex ★ 6,505repo stars performance-engineer performance-engineer — a subagent for diagnosing slow requests, critical paths, and rendering regressions. Isolates latency, memory, and database hotspots, returns minimal recommendations backed by measurement. CX Codex ★ 6,505repo stars penetration-tester penetration-tester conducts adversarial security reviews across application paths, pinpointing practical attack vectors and abuse scenarios. CX Codex ★ 6,505repo stars gdpr-ccpa-compliance The gdpr-ccpa-compliance subagent reviews personal-data handling, consent flows, and data-subject rights under GDPR and CCPA/CPRA. Use it when an implementation needs a compliance check. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open