Deep QA

Use when reviewing, auditing, QAing, critiquing, verifying, or assessing any artifact — a spec, code change, diff, PR, research report, skill, prompt, or document. Also use for pre-completion verification ("verify this works", "prove this is done", "evidence before claiming complete"). Trigger phrases include "review this", "audit this", "QA this", "find issues", "find defects", "critique this", "check this for problems", "what's wrong with this", "evaluate this", "run QA", "review the diff", "review the PR", "review my code", "deep QA", "defect audit", "code review", "assess this", "verify th

5 stars 1 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add npow/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add npow/claude-skills --skill deep-qa
Manual install
git clone --depth 1 https://github.com/npow/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/deep-qa ~/.claude/skills/deep-qa

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Deep QA Skill

Systematically audit an existing artifact for defects using parallel critic agents across QA dimensions tailored to the artifact type. Unlike deep-design (which designs and iterates) or deep-research (which explores the web), deep-qa takes an artifact as-is and finds what's wrong with it.

**No spec drafting. No redesign. Find and report.**

## Execution Model

**Pressure awareness:** this skill applies the pressure circuit breakers from [`_shared/pressure-awareness.md`](../_shared/pressure-awareness.md). After each critic round, check for diminishing returns (round N < 20% of round N-1 findings → eligible for early termination). After 3 rounds with < 20% new findings, stop rather than grinding.

Shares deep-design's core execution contracts:

- **All data passed to agents via files, never inline.** Artifact, known-defects list, angle definitions — all written to disk before spawning.
- **State written before agent spawn, not after.** `spawn_time_iso` written before Agent tool call. Spawn failure records `spawn_failed` status.
- **Structured output is the contract; free-text is ignored.** Severity judges produce machine-parseable structured lines. Unparseable output → fail-safe critical.
- **No coordinator self-review of anything load-bearing.** Severity classification delegated to independent judge agents.
Read the full skill on GitHub

Details

Skill name
deep-qa
Path
deep-qa/SKILL.md
License
Apache-2.0
Repo updated
20 August 2026

FAQ

What does the Deep QA skill do?

Use when reviewing, auditing, QAing, critiquing, verifying, or assessing any artifact — a spec, code change, diff, PR, research report, skill, prompt, or document. Also use for pre-completion verification ("verify this works", "prove this is done", "evidence before claiming complete"). Trigger phrases include "review this", "audit this", "QA this", "find issues", "find defects", "critique this", "check this for problems", "what's wrong with this", "evaluate this", "run QA", "review the diff", "review the PR", "review my code", "deep QA", "defect audit", "code review", "assess this", "verify th

How do I install the Deep QA skill?

Claude Code plugin: /plugin marketplace add npow/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Deep QA popular?

It lives in npow/claude-skills, which has 5 GitHub stars and 1 forks.

Related skills

Autopilot

5

npow/claude-skills

Use when the user says "autopilot", "build this", "make it", "ship it", "just do it", "do it", "implement this", or gives a vague idea, spec, task list, or bug fix and expects autonomous execution. Handles decomposition, agent coordination, and verification automatically. "build me end to end", "go from idea to code", "do everything", "run this autonomously". Follows the Spec-Driven Development workflow: specify → clarify → plan → tasks → analyze → implement.

Productivity & Notes

Build Python Library

5

npow/claude-skills

Implements pip-installable Python libraries from scratch using src layout, pyproject.toml, and pytest. Use when the user asks to build, create, implement, or scaffold a Python library, package, pip package, middleware, SDK, or wrapper. Covers project scaffolding, proxy/wrapper patterns, provider-agnostic interfaces, async/sync support, and test infrastructure.

Software Development

Canon Design Review

5

npow/claude-skills

Architecture-level design review evaluating 15 Tier 2 best practices drawn from DDD (Evans), POEAA (Fowler), Release It! (Nygard), DDIA (Kleppmann), Team Topologies (Skelton/Pais), How Buildings Learn (Brand), and Systemantics (Gall). Auto-invoke when a PR touches: - Service definitions, infrastructure code, API boundaries, or database schemas - Files matching **/architecture*, **/design*, **/api/*, **/schema*, **/migrations/* - Any directory named services/, infrastructure/, platform/, domain/, core/ Also invoke when the user says: - "design review", "architecture review", "review the design"

Software Development

Deep QA Ensemble V1

5

npow/claude-skills

Use when the user asks to review with ensemble judges, or explicitly requests the ensemble variant of deep-qa. Benchmark variant that uses three heterogeneous providers for severity judging instead of a single judge. Same triggers as deep-qa but with multi-provider ensemble scoring.

Testing & QA

CI Health Report

5

npow/claude-skills

Use when checking CI/CD health, Jenkins build failures, flaky tests, build success rates, or generating a CI health report. Trigger phrases: CI health, build failures, jenkins report, flaky tests, build health, are builds passing, CI status.

Testing & QA

Flaky Test Diagnoser

5

npow/claude-skills

Systematically diagnoses why a test is flaky by running multi-run experiments, isolation tests, ordering permutations, and timing analysis. Use when the user says a test is flaky, intermittent, non-deterministic, randomly failing, passes sometimes, or asks to debug test flakiness.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.