reviewer-protocol

Orchestrates reviewer-driven rejection workflows with enforced non-author revision lockouts.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill reviewer-protocol-golnaz89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill reviewer-protocol-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol enforces a strict revision workflow where a Reviewer can approve or reject work, and a locked-out original author cannot self-revise after rejection, ensuring independent revision.

Core Features & Use Cases

  • Rejection-driven revisions: On rejection, a different agent is assigned to revise the artifact, preventing self-editing by the original author.
  • Escalation for expertise: If needed, escalate to a new agent with specific expertise to address the rejection.
  • Strict lockout semantics: The original author is barred from contributing to the revision; the revision is owned by another agent until approval.
  • Use cases include code reviews, design artifacts, and other artifacts requiring independent remediation following reviewer feedback.

Quick Start

Spawn a revision task for a non-original author when a reviewer rejects.

Frequently Asked Questions about reviewer-protocol

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

FAQPage Schema
How do I enforce independent code review revisions after rejection?

Independent code review revisions after rejection are enforced by applying lockout semantics that bar the original author from self-editing. The protocol assigns the rejected artifact to a different agent, ensuring strict reviewer-driven remediation before approval.

What is a reviewer-led rejection workflow with author lockout?

A reviewer-led rejection workflow with author lockout is a governance protocol where a reviewer rejects an artifact and the original author is prohibited from revising it. A new agent is spawned to own the revision cycle until the reviewer approves.

How do I escalate a code review rejection to a different agent?

Escalating a code review rejection to a different agent is handled by spawning a revision task for a non-original author upon rejection. The protocol validates the new agent before assigning the revision, ensuring independent remediation.

Can I use this review lockout protocol for content and design artifacts?

This review lockout protocol can be used for content and design artifacts. It orchestrates reviewer-driven rejection workflows across code, content, and artifact reviews where independent remediation and strict author lockouts are required.

Does the reviewer protocol support reassigning revisions to agents with specific expertise?

The reviewer protocol supports reassigning revisions to agents with specific expertise. It automates agent validation before spawning the revision, allowing escalations to specialized agents while maintaining the original author lockout.

What are the limitations of preventing original authors from self-revising rejected work?

Preventing original authors from self-revising rejected work limits rapid self-correction but ensures independent remediation. The strict lockout semantics mean the original author cannot contribute to the revision until the reviewer approves the new agent's work.