How do I install the Peer QA Review skill?

Run npx skillmds@latest add netresearch/peer-qa-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Peer QA Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Peer QA Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Peer QA Review free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under (MIT AND CC-BY-SA-4.

Who published Peer QA Review?

netresearch (@netresearch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Peer QA Review by netresearch — Agent Skill

Name: Peer QA Review
Rating: 4.666666666666667 (3 reviews)
Author: netresearch

Peer QA Review

Use when reviewing a teammate's completed work as Round-1 IT QA (before customer acceptance / QA2 / internal close). Triggers: tickets moved to QA, 'ready for QA' / 'ready for review' comments, or requests for 'IT QA review' / 'peer review' / 'internal QA' / 'quality gate'. Covers a 6-stage lifecycle, severity vocabulary, comment template, edge cases, anti-patterns. Generic for any IT/Ops team.

netresearch Updated Sep 17, 2026

File contents

Peer QA Review (Round 1)

A teammate marked work ready for QA. Verify before it reaches customer acceptance, QA2, or close: re-run verification; check formal correctness, inventory, docs; post a structured comment; transition. Not rubber-stamping; detail in references/.

When it applies

Triggers: see description. Skip if: still In Progress (transition first); already QA2 (different scope); already closed (post-mortem only); or you are the implementer (no self-review; per-PR, §E).

A ticket-system skill is required (Jira: jira-communication) for Stage 0 discovery. Consult maintenance skills for overrides.

Lifecycle

-1 Claim — your FIRST tool call, before Stage 0: assign to yourself; someone else's, stop; never self-review (lifecycle.md §-1).
0 Discover: ${CLAUDE_SKILL_DIR}/scripts/qa-gather.sh <KEY> (--json to parse).
1 Formal (description, linkage, console-output, worklog); 2 Functional, Inventory, Guardrails (re-run; update inventory; check adjacent components, shared-layer downstream, default path); 3 Docs, Rollback, Communication.
4 Verdict (routing below); 5 Comment, Transition, Worklog: internal QA comment; on QA2 also a customer handover.

Severity icons

Reuse the Atlassian set. (/) passed; (x) MUST/blocking (bounce); (!) SHOULD (document, follow-up if structural); (i) hint; (?) open question (block); (off) n/a (never (-) or *n/a*).

Output

One internal QA comment: header h3. IT Internal QA, h4 per pillar, severity icons, a verdict line.

On a QA2 verdict, post a second, separate comment: the customer handover. The internal QA comment is addressed to IT and never states the acceptance check, leaving the approver lost. The handover is plain (no jargon or icons): what was delivered, the one acceptance check, the next step.

Verdict routing

Pass, resolve: all (x) clear, IT-internal; QA to the project's terminal reviewed status — usually Resolved — then clear your assignment. Take the status from the transition list, not from this line: closing is frequently someone else's step, so a reviewer who walks a ticket further than the pass requires has changed something that was not theirs to change.
Pass, QA2: all (x) clear, customer-affecting; post the QA comment and a customer handover; QA to QA2, assign the product owner.
Bounce: any (x); QA to In Progress, comment the blocker, reassign.
Won't-do: blocking external prerequisite; document, file a follow-up, resolve Won't-do with a reopen condition.

When uncertain, default to QA2.

Anti-patterns

The cardinal one: no re-execution by the reviewer — copy-pasting the implementer's output is not QA. Others (giant final comments, Jira Markdown leakage, end-of-run inventory, tags without a green pipeline) in references/anti-patterns.md.

References

references/lifecycle.md, references/checklist.md (checks by pillar); references/severity.md; references/comment-template.md (template, examples, customer handover); references/edge-cases.md (QA2 routing, bounce, won't-do, self-review); references/anti-patterns.md; references/batch-review.md (≥6 tickets, sub-agents).

---name: peer-qa-reviewdescription: Use when reviewing a teammate's completed work as Round-1 IT QA (before customer acceptance / QA2 / internal close). Triggers: tickets moved to QA, 'ready for QA' / 'ready for review' comments, or requests for 'IT QA review' / 'peer review' / 'internal QA' / 'quality gate'. Covers a 6-stage lifecycle, severity vocabulary, comment template, edge cases, anti-patterns. Generic for any IT/Ops team.license: (MIT AND CC-BY-SA-4.0). See LICENSE-MIT and LICENSE-CC-BY-SA-4.0---# Peer QA Review (Round 1)A teammate marked work **ready for QA**. Verify before it reaches customeracceptance, QA2, or close: re-run verification; check formal correctness,inventory, docs; post a structured comment; transition. Not rubber-stamping;detail in `references/`.## When it appliesTriggers: see description. **Skip** if: still In Progress (transitionfirst); already QA2 (different scope); already closed (post-mortem only); or youare the implementer (no self-review; per-PR, §E).A ticket-system skill is required (Jira: `jira-communication`) for Stage 0discovery. Consult maintenance skills for overrides.## Lifecycle- **-1 Claim — your FIRST tool call**, before Stage 0: assign to yourself; someone else's, stop; never self-review (`lifecycle.md` §-1).- **0 Discover**: `${CLAUDE_SKILL_DIR}/scripts/qa-gather.sh <KEY>` (`--json` to parse).- **1 Formal** (description, linkage, console-output, worklog); **2 Functional, Inventory, Guardrails** (re-run; update inventory; check adjacent components, shared-layer downstream, default path); **3 Docs, Rollback, Communication**.- **4 Verdict** (routing below); **5 Comment, Transition, Worklog**: internal QA comment; on QA2 also a customer handover.## Severity iconsReuse the Atlassian set. `(/)` passed; `(x)` MUST/blocking (bounce); `(!)`SHOULD (document, follow-up if structural); `(i)` hint; `(?)` open question(block); `(off)` n/a (never `(-)` or `*n/a*`).## OutputOne internal QA comment: header `h3. IT Internal QA`, h4 per pillar,severity icons, a verdict line.**On a QA2 verdict, post a second, separate comment: the customer handover.**The internal QA comment is addressed to IT and never states the acceptancecheck, leaving the approver lost. The handover is plain (no jargon or icons):what was delivered, the one acceptance check, the next step.## Verdict routing- **Pass, resolve**: all `(x)` clear, IT-internal; QA to the project's terminal reviewed status — usually **Resolved** — then clear your assignment. Take the status from the transition list, not from this line: closing is frequently someone else's step, so a reviewer who walks a ticket further than the pass requires has changed something that was not theirs to change.- **Pass, QA2**: all `(x)` clear, customer-affecting; post the QA comment **and** a customer handover; QA to QA2, assign the product owner.- **Bounce**: any `(x)`; QA to In Progress, comment the blocker, reassign.- **Won't-do**: blocking external prerequisite; document, file a follow-up, resolve Won't-do with a reopen condition.When uncertain, default to QA2.## Anti-patternsThe cardinal one: **no re-execution by the reviewer** — copy-pasting theimplementer's output is not QA. Others (giant final comments, Jira Markdownleakage, end-of-run inventory, tags without a green pipeline) in`references/anti-patterns.md`.## References`references/lifecycle.md`, `references/checklist.md` (checks by pillar);`references/severity.md`; `references/comment-template.md` (template, examples,customer handover); `references/edge-cases.md` (QA2 routing, bounce, won't-do,self-review); `references/anti-patterns.md`; `references/batch-review.md`(≥6 tickets, sub-agents).

Frequently asked questions