Peer QA Review
Round-1 IT QA peer-review runbook: lifecycle, checklist, severity vocabulary, structured Jira comment template, edge cases, anti-patterns. Triggers on QA-status tickets, 'ready for QA' comments, and explicit IT QA / peer review / quality gate requests. Generic; defers to team-specific overrides.
Install
Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.
-
Claude Code via this marketplace /plugin install peer-qa-review@netresearch-claude-code-marketplaceFirst add the marketplace once in Claude Code:
/plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, seeClaude Code plugin setupA plugin can include several skills and additional components. -
npx interactive skill selection npx skills add https://github.com/netresearch/peer-qa-review-skillRequires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Uses the skills CLI from
skills.shInstalls skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route. -
composer require PHP project, as a package composer require netresearch/peer-qa-review-skillAllow the Composer skill installer to activate and approve skill registration when prompted. Requires
netresearch/composer-agent-skill-pluginDiscovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup. -
composer skills:add PHP project, direct source composer skills:add netresearch/peer-qa-review-skillInstall and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by
netresearch/composer-agent-skill-pluginPins source repositories without a Packagist package and records them incomposer.skills.lock. Runtime dependencies remain separate.
What you can do with it
- Round-1 IT QA peer-review runbook: lifecycle, checklist, severity vocabulary, structured Jira comment template, edge cases, anti-patterns
- Triggers on QA-status tickets, 'ready for QA' comments, and explicit IT QA / peer review / quality gate requests
- Generic; defers to team-specific overrides
What you get back
- A structured QA comment with severity, supporting evidence and a clear verdict on the next ticket status.
What it expects in your project
Check the source README for current examples, requirements and limitations. Open full README