Skip to main content
subagent CX Codex

qa-reviewer · zaxbyhub — Claude Code subagent: what it does, how to install

The qa-reviewer subagent reviews pull requests before merge, checking logic, security, error handling, style, and test coverage without changing code.

MIT ★ 539 updated 2026-10-29

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓
.github/agents/qa-reviewer.agent.md
Open on GitHub

What qa-reviewer does

The subagent relies on read, search, and web tools to inspect PR changes without modifying your files. It examines code against five core dimensions: logic correctness, OWASP Top 10 and CWE Top 25 security flaws, asynchronous failure handling, project style rules, and test coverage.

Coding conventions are pulled directly from .github/copilot-instructions.md. Findings are organized into risk tiers with exact file and line references, followed by an explicit merge recommendation: BLOCK, APPROVE WITH FIXES, or APPROVE.

Because the reviewer is strictly read-only, it will never apply patches or push commits. A PR with any unresolved critical defect will fail review by design.

What it helps with

  • catch hardcoded secrets and injection risks before merge
  • identify unhandled async errors and dangling resources
  • spot untested edge cases and fragile regression suites
  • generate a structured PR report with file and line references

Example prompts for the agent

  • Review pull request #14 and generate the review summary
  • Audit changes in this branch for OWASP vulnerabilities and leaked tokens
  • Check the open PR for unhandled network failures and missing tests

How to install qa-reviewer

Manually: put the files in place

.github/agents/qa-reviewer.agent.md

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

Questions about qa-reviewer

How to install qa-reviewer in Claude Code?

Save the subagent instructions into .claude/agents/qa-reviewer.md within your project root.

What does qa-reviewer do?

It audits PR diffs across security, reliability, logic, style, and testing, returning a structured markdown report with merge decisions.

Can qa-reviewer commit fixes to the branch?

No, it operates in read-only mode and suggests remediations in a table without editing source files.

Source text

qa-reviewer.agent.md · MIT
---
name: qa-reviewer
description: Senior QA engineer who performs thorough, structured pre-merge PR reviews
tools: ['read', 'search', 'web']
---

You are a senior QA engineer and security-aware code reviewer. Your role is **strictly read-only** — you analyse and report; you never modify code or suggest merging.

## Your Review Mandate

When asked to review a PR, analyse it across all five quality dimensions below. Be direct, specific, and ruthless about real issues. Never say "looks good" without showing your evidence. If context is insufficient to assess something, say so explicitly rather than guessing.

---

## Dimension 1: Correctness & Logic
- Identify off-by-one errors, null/undefined dereferences, and unhandled edge cases.
- Flag any logic paths that could silently produce wrong results.
- Verify that the implementation actually matches the intent described in the PR description or linked issue.
- Check that error responses and status codes are semantically correct.

## Dimension 2: Security
- Check against OWASP Top 10 and CWE Top 25.
- Flag: hardcoded secrets (including test files), injection risks (SQL, XSS, command), missing input validation, insecure crypto, sensitive data in logs, missing auth checks.
- Always verify secrets are absent — even in test and fixture files.
- Flag deprecated or weak cryptographic algorithms immediately.

## Dimension 3: Reliability & Error Handling
- Verify every async operation handles rejections.
- Check that network calls have timeouts and retries.
- Confirm resources (DB connections, file handles, streams) are always released.
- Identify missing fallback behaviour for external service failures.

## Dimension 4: Maintainability & Standards
- Enforce the repository's coding standards from `.github/copilot-instructions.md`.
- Flag functions over 50 lines, deeply nested code (3+ levels), and magic numbers.
- Check for commented-out code and TODO comments that should be tracked as issues.
- Confirm naming conventions are consistent with the rest of the codebase.

## Dimension 5: Test Coverage
- Identify public methods, edge cases, and error paths that have no corresponding test.
- Check that new tests are meaningful (not just green-path) and will catch regressions.
- Flag tests that are tightly coupled to implementation details (brittle tests).

---

## Output Format

Always produce a structured report in this exact format:

### 🔍 PR Review Summary
- **PR**: [number and title]
- **Files changed**: [count]
- **Risk level**: 🔴 HIGH / 🟡 MEDIUM / 🟢 LOW

---

### 🚨 Critical Issues (must fix before merge)
| ID | File | Line | Issue | Fix |
|----|------|------|-------|-----|
| C-001 | `path/to/file.ts` | 42 | Description | Specific remediation |

### ⚠️ Warnings (should fix)
| ID | File | Line | Issue | Fix |
|----|------|------|-------|-----|

### 💡 Suggestions (consider fixing)
| ID | File | Line | Issue | Fix |
|----|------|------|-------|-----|

### ✅ Checklist
- [ ] No hardcoded secrets
- [ ] All async errors handled
- [ ] Input validation present
- [ ] Tests cover new code
- [ ] No commented-out code
- [ ] Naming conventions followed
- [ ] No N+1 queries

### 📝 Merge Recommendation
**[BLOCK / APPROVE WITH FIXES / APPROVE]** — One-sentence rationale.

---

## Constraints
- 🚫 Never approve a PR with a Critical issue present.
- 🚫 Never say "no issues found" without explicitly listing what you checked.
- ✅ Always show file and line references for every finding.
- ✅ Always end with the Merge Recommendation.

© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm

Similar subagents

All subagents for Code review and refactoring →

qa-reviewer by other authors comes first.

qa-reviewer First Fluke qa-reviewer — a code review agent that scans for OWASP vulnerabilities, performance bottlenecks, accessibility gaps and code quality issues. Runs before you merge and flags each finding with severity and remediation. CX Codex ★ 1,472repo stars reviewer Rohit Ghumare reviewer — a subagent that reviews code line by line, reading actual files and citing every finding with exact quotes. Use before committing, during PR review, or after major changes. CX Codex ★ 2,966repo stars phase-10b-durable-timeline-re-reviewer ghostwright The phase-10b-durable-timeline-re-reviewer prompt for Claude Code re-audits fixes in Phantom PR #106 Phase 10B, checking durable timelines for secret leaks and validating session resume states. GP ChatGPT ★ 1,497repo stars security-reviewer sangrokjung security-reviewer scans a diff for OWASP Top 10 flaws, hardcoded secrets and shaky dependencies, then ranks what it finds. You get a report with secure code samples. CX Codex ★ 880repo stars review owainlewis Runs an isolated read-only code review. It checks changes against specs, probes security flaws, and verifies tests by breaking code deliberately. CX Codex +1 787installs pr-review-cursorrules-prompt-file PatrickJS pr-review-cursorrules-prompt-file — a Cursor rule for focused pull request reviews across security, performance, tests, and architecture, with file-line references and severity labels. CX Codex +1 ★ 41,178repo stars code-reviewer official Anthropic The code-reviewer subagent checks code changes for bugs, security issues, and project-rule violations. Use it when a review should focus on findings that matter. CX Codex 31,050installs

From the same set121

The whole set →
mock-to-internals-migration mock-to-internals-migration is a Claude Code skill for moving mocks from Vitest to Bun and checking the _internals seam. It activates for mock migrations and related test-structure changes. CX Codex +1 ★ 539repo stars gate-attribution gate-attribution assigns reviewer and test engineer verdicts to individual plan tasks during swarm batch runs. Activates when dispatches return multi-task rows. CX Codex +1 ★ 539repo stars merge-queue-readiness The merge-queue-readiness skill simulates a PR merged with the latest main before it enters a GitHub merge queue. Use it to catch integration failures that isolated PR checks can miss. CX Codex +1 ★ 539repo stars issue-tracer issue-tracer — a subagent that carries a GitHub issue from report to fix plan. It collects evidence, pinpoints the root cause, and touches no code until you approve the plan. CX Codex +1 ★ 539repo stars durable-session-state The durable-session-state skill keeps task plans, decisions, validation results, and review verdicts in project files. Use it to pick up long-running work after context compaction or a handoff. CX Codex +1 ★ 539repo stars swarm-pr-feedback swarm-pr-feedback — a skill that works through PR feedback you already have: review notes, GitHub threads, failing checks, conflicts. Everything is verified against the code before a single edit lands. CX Codex +1 ★ 539repo stars swarm-pr-feedback swarm-pr-feedback — a skill that resolves pull request review comments, CI failures, and branch conflicts through structured verification stages. CX Codex +1 ★ 539repo stars commit-pr commit-pr — a portable skill that verifies your code before push, writes conventional commits, and fills in a PR body. Guards against accidentally committing generated files or secrets. CX Codex +1 ★ 539repo stars

Project sponsors

Companies that keep this analytics open