Claude Plugins for Testing: A Guide

Overview

The testing category on ClaudePluginHub holds 4,106 plugins — one slice of a 32,603-plugin directory. Category membership is loose by design: a plugin lands in testing if its components, manifest keywords, or repository description touch on tests, QA, or verification workflows. That includes plugins built specifically for QA work, and plugins where testing is one capability among many.

This guide walks the category as it stands today, anchored to install counts and component breakdowns rather than blanket endorsements. If you want to browse the full list yourself, head to the testing category page; the rest of this post pulls out plugins worth a closer look and explains what each one ships.

Why This Category

Testing surfaces in Claude Code through a few different shapes. Some plugins package QA workflows directly — Playwright drivers, pytest patterns, code review checklists, TDD enforcement. Others are broader full-stack toolkits where testing is one of many concerns, and they get categorized into testing because their skills mention test generation alongside other tasks.

That distinction matters when you are shopping. If you want a plugin that exists to enforce a testing methodology, look for narrow scopes: a QA bundle, a TDD workflow, a CLAUDE.md audit tool. If you want broader help and testing is one piece, the full-stack and "everything" bundles cover the surface area but at the cost of focus.

Skills dominate the directory. Of the 305,372 components indexed across all plugins, 180,306 are skills — roughly 59% of every component on the platform — and that ratio holds inside the testing category, since most QA workflows ship as skill packages rather than commands or hooks.

Plugins to Consider

Five plugins from the testing category surfaced as having either real install pull, distinctive scope, or both. Each is linked to its detail page on the directory.

antigravity-bundle-qa-testing — 37,904 stars on the source repo. Components: skills. The most narrowly scoped plugin on this list. It implements a complete QA and testing workflow, including A/B test gating with hard gates, browser test automation through Playwright and Puppeteer, code review checklists, TDD enforcement, systematic debugging, and pytest patterns for fixing failing tests. If you want Claude Code to behave like a QA engineer rather than an everything-engineer, this is the closest match in the category.

claude-md-management — 46 installs in the last 7 days, 20,139 stars on the source repo. Components: commands, skills. Not a test runner — instead, it audits CLAUDE.md files across repositories by discovering them with find, evaluating quality against rubrics, generating reports, and applying targeted improvements after approval. It also captures learnings from Claude Code sessions to propose concise updates to CLAUDE.md or .claude.local.md. It lands in the testing category because it ships rubric-based verification flows; treat it as a documentation-QA tool, not a code-test tool.

fullstack-dev-skills — 65 installs in the last 7 days, 9,269 stars. Components: commands, skills. A broader full-stack toolkit that empowers Claude with expertise across multiple languages, frameworks, and cloud platforms, covering code generation, debugging, architecture design, DevOps automation, testing, security audits, and project management. Testing is one of several skills it bundles, so install it if you want general full-stack coverage and accept that the testing surface will not be as deep as a dedicated QA plugin.

everything-claude-code — 51 installs in the last 7 days, 2 stars on the source repo. Components: commands, agents, skills, hooks, MCP. The widest component coverage of any plugin on this list — it ships every major component type the platform supports. Low star count means the upstream repo is new or lightly trafficked; the install pull suggests early adopters are trying it out. Worth watching, but not a safe pick if you need a battle-tested QA workflow.

godot-skills — 98 installs in the last 7 days, 30 stars. Components: skills. A Godot-engine skill bundle that surfaces in this category because game-development workflows include scene testing and runtime checks. Useful only if you work in Godot; the rest of the testing category is engine-agnostic.

Notable Patterns

A few things are worth flagging if you scan the testing category broadly:

• Skills-only bundles outnumber multi-component plugins. Four of the five plugins above ship only skills (or skills plus commands). Only everything-claude-code adds agents, hooks, and an MCP server. If you want hook-based gating — say, blocking a commit when tests fail — your pool is smaller than the 4,106 category size suggests.
• Star count and install count rarely line up. antigravity-bundle-qa-testing has 37,904 stars on its source repository but a smaller 7-day install profile than godot-skills, which has 30 stars. Stars track GitHub-side popularity of the underlying project; installs track how many ClaudePluginHub users actually pulled the plugin into their setup in the last week. Both signals are useful — they answer different questions.
• Category membership is loose. The 4,106 number includes plugins where testing is one of many capabilities. fullstack-dev-skills, for example, is here because its skill set mentions test scaffolding alongside DevOps and architecture. Read the category size as "4,106 plugins where testing shows up somewhere," not "4,106 plugins dedicated to testing."
• Long-tail noise is real. The category also contains 0-star, skill-only plugins that get tagged through keyword overlap rather than focus. Filtering by install count or star count surfaces the active subset quickly, which is what the directory's sort options are for.

Wrap-up

If you want a focused QA workflow, start with antigravity-bundle-qa-testing. If you want general full-stack help that happens to include testing, jeffallan-fullstack-dev-skills is the higher-star option in this category. For CLAUDE.md audit flows, claude-md-management is purpose-built. Browse the full testing category or the wider plugins directory for adjacent picks; the same filter pattern works across deployment, development, and other categories.