worker-reviewer-pipeline

Orchestrate iterative implementation and review cycles between worker and reviewer agents.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill worker-reviewer-pipeline-hiddink-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker-reviewer-pipeline
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/worker-reviewer-pipeline
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill worker-reviewer-pipeline-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of low-quality code merges by enforcing a rigorous, iterative review cycle between a worker agent and a reviewer agent, ensuring that complex changes meet strict quality standards before finalization.

Core Features & Use Cases

  • Iterative Quality Gates: Automatically cycles between implementation and review until defined quality criteria are met.
  • Specialized Agent Roles: Supports distinct agent configurations for implementation and review, allowing for model-specific optimization (e.g., Sonnet for coding, Opus for review).
  • Use Case: When implementing security-critical features like authentication or payment gateways, this pipeline ensures that every change is vetted by a secondary agent, reducing the likelihood of bugs or vulnerabilities reaching the main branch.

Quick Start

Activate the worker-reviewer-pipeline to implement the new payment gateway feature using the security-critical template.

Frequently Asked Questions about worker-reviewer-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review and quality assurance for complex feature integration?

Automated code review and quality assurance can be orchestrated through an iterative workflow between specialized worker and reviewer AI agents. This pipeline cycles implementation and review continuously until strict quality gates are satisfied before finalization.

What is the best way to ensure code quality in security-critical refactoring tasks?

Code quality in security-critical refactoring is enforced by a rigorous, iterative review cycle between a worker agent and a reviewer agent. This ensures complex changes meet strict quality standards by vetting every change with a secondary agent before merging.

How does a multi-agent pipeline handle continuous feedback loops for code review?

A multi-agent pipeline handles continuous feedback loops by executing sub-agent tasks with bypassed permissions, allowing an automated reviewer to continuously evaluate the worker's implementation output until defined quality criteria are met.

Can I use different AI models for implementation and review in an automated quality assurance pipeline?

Different AI models can be used for implementation and review by configuring distinct specialized agent roles. This allows model-specific optimization, such as using Sonnet for coding implementation and Opus for the review phase.

When do I need an iterative worker-reviewer pipeline for my development workflow?

An iterative worker-reviewer pipeline is needed for high-stakes development tasks like security-critical refactoring, complex feature integration, and performance-sensitive updates to reduce the likelihood of bugs or vulnerabilities reaching the main branch.

How to prevent low-quality code merges when automating complex feature integration?

Preventing low-quality code merges requires an automated pipeline that enforces a rigorous iterative review cycle between implementation and review agents, ensuring complex changes meet strict quality standards before finalization.