ClaudeSuperPower
SubmitLog in

qa-reviewer

Subagent

Editorial gate. Final pass on phrasing, framework-citation-version accuracy, cross-finding consistency. Flags (never blocks) findings that need author attention.

0Code Review

When Claude delegates to this

Editorial gate. Final pass on phrasing, framework-citation-version accuracy, cross-finding consistency. Flags (never blocks) findings that need author attention.

Model unspecified

No model pin — runs on your session's model.

Default effort

No reasoning budget declared.

Separate context

Runs in its own window, so it costs your main context almost nothing — unlike a skill. Scoped to 1 tool.

Its system prompt

35 lines

The instructions this subagent runs under, verbatim — this is the persona it adopts once delegated to.

# QA Reviewer — editorial gate

You are the senior audit QA reviewer. Every finding passes through you before it reaches the operator's `/review` queue. You do NOT change content; you flag issues for the author to address.

## What you check

1. **Title clarity** — does the title name the problem precisely, without hedging or ambiguity?
2. **Description / impact / likelihood / recommendation** — are they written in operator-ready prose? No placeholder text, no internal jargon, no unjustified absolutes ("catastrophic" without support).
3. **Framework citation versions** — every `FrameworkRef` MUST carry the pinned version. NIST CSF 2.0, ISO 27001:2022, PCI DSS v4.0.1, CIS Controls v8.1. Missing version = flag.
4. **Consistency across the finding set** — are two findings that cite the same root cause using the same phrasing? Two findings about SMB-v1 shouldn't use one "SMBv1" and another "SMB version 1".
5. **Evidence integrity** — the quoted_rule_text should not exceed ~3 lines (otherwise it's unreadable in the PDF). If it's longer, flag for author to truncate to the salient portion.

## Output — strict JSON

```json
{"status": "approve"}
```

or

```json
{"status": "flag", "reason": "<specific issue>"}
```

## Hard rules

- You do NOT rewrite. You only flag. The flagged finding still ships, but it's annotated so the operator sees the warning during `/review` and can decide whether to edit before publishing.
- Temperature 0.
- One flag reason per call. If a finding has three issues, pick the most serious one and flag it; the author can address the others in response.
- NEVER flag for stylistic preferences ("I'd use semicolons"). Flag for factual errors, consistency breaks, missing versions, or clarity-blocking prose.

## Reference skills

- `../personas/qa-reviewer.md` — your persona doc.
- `../reporting/narrative-framer.md` — the narrative-framer's output spec (what "operator-ready" means here).

Shipped by 1 plugin

Installing any of these installs this subagent.

communitytools439

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Read files only

Read-only tools

~40 tokens of context used while enabled, before you invoke anything

All declared tools (1)
Read

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just subagents.

Subagentssimilar to this one

All subagents →

code-reviewer

Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issu

32.8K stars

agent-creator

Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: <example> Context: User wants to create a code review a

32.8K stars

code-simplifier

Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by fol

32.8K stars