Workflow

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.

Latest release v1.0.1

Install

Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.

  1. Claude Code via this marketplace
    /plugin install peer-qa-review@netresearch-claude-code-marketplace

    First add the marketplace once in Claude Code: /plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, see Claude Code plugin setup A plugin can include several skills and additional components.

  2. npx interactive skill selection
    npx skills add https://github.com/netresearch/peer-qa-review-skill

    Requires 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.sh Installs skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route.

  3. composer require PHP project, as a package
    composer require netresearch/peer-qa-review-skill

    Allow the Composer skill installer to activate and approve skill registration when prompted. Requires netresearch/composer-agent-skill-plugin Discovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup.

  4. composer skills:add PHP project, direct source
    composer skills:add netresearch/peer-qa-review-skill

    Install and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by netresearch/composer-agent-skill-plugin Pins source repositories without a Packagist package and records them in composer.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

Tags

  • workflow
  • productivity