reviewer-protocol

Enforce author lockout and reassign revisions to different agents after rejection.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill reviewer-protocol-leep-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill reviewer-protocol-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a Reviewer rejects work, teams risk defensive loops where the original author attempts self-revision. This Skill enforces strict lockout semantics and a deterministic revision handoff to a different agent or escalation path.

Core Features & Use Cases

  • Enforces lockout: the original author is prevented from producing the next revision.
  • Reassignment or escalation: on rejection, a different agent is assigned, or a new expert is spawned.
  • Coordinator-driven: all changes are enforced mechanically by the Coordinator to prevent bypass.

Quick Start

Implement the reviewer-protocol to lock out the original author after a rejection and reassign the revision to a different agent.

Frequently Asked Questions about reviewer-protocol

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

FAQPage Schema
How do I prevent an author from revising their own work after a code review rejection?

To prevent author self-revision after a code review rejection, enforce a strict revision lockout that mechanically blocks the original contributor and requires a different agent to handle the revision.

What is a reviewer-driven lockout protocol for artifact revisions?

A reviewer-driven lockout protocol for artifact revisions is a deterministic workflow mechanism where a coordinator mechanically prevents the original author from submitting revisions, forcing reassignment to a different agent or an escalation path.

How do I reassign a rejected document revision to a different agent deterministically?

To reassign a rejected document revision deterministically, implement a coordinator-driven handoff that mechanically selects a different agent or spawns a new domain expert, bypassing the original author entirely.

Does the reviewer-protocol support escalating revisions for domain expertise?

Yes, the reviewer-protocol supports escalating revisions for domain expertise by spawning a new expert agent when a rejection occurs, ensuring the revision handoff targets the required domain knowledge.

Can I use a coordinator to enforce code review constraints across different teams?

Yes, you can use a coordinator to enforce code review constraints across different teams, as the lockout and reassignment logic is mechanically enforced and applicable to code reviews, document reviews, and artifact revisions.

Why do post-rejection work loops happen and how can a revision lockout stop them?

Post-rejection work loops happen when original authors attempt defensive self-revisions after being rejected. A revision lockout stops them by mechanically blocking the author and forcing a different agent to produce the next revision.