Adversarial QA
Drives a repo to measured test-hardening convergence.
About
A skill that pushes a repository toward objective test-hardening goals: coverage, mutation testing, fuzzing, and load/soak runs, repeating until measurable thresholds are met.
It is designed to be resumable, so long hardening campaigns can pick up where they left off. Expect heavy compute on large repos — this is a thoroughness-first workflow, not a quick pass.
What it can do
- Coverage measurement and gap analysis
- Mutation testing
- Fuzzing campaigns
- Load and soak testing
- Resumable hardening runs
- Objective convergence thresholds
Setup
- Add the marketplace to Claude Code.
- Install the adversarial-qa plugin.
- Run it against a repo and let it iterate toward the coverage and hardening thresholds.
Prerequisites
A code repository with an existing test runner.
Use cases
Works with
Trust score — 5/10
Scored 5/10 (metrics tier, metrics-v1). Evidence: 1 star on the catalog repo, very early; mutation testing and fuzzing are compute-heavy on large repos; resumable runs help long campaigns. License: MIT.
★ 1 GitHub stars
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 3.0/10
- Maintenance · recency, releases, issue load
- 5.0/10
- Openness · license + docs
- 8.0/10
- Manual review · sanity read + red-flag check
- 6.0/10
- · 1 star on the catalog repo, very early
- · mutation testing and fuzzing are compute-heavy on large repos
- · resumable runs help long campaigns
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.