reviewer-protocol

Enforces rejection lockout and reassigns revisions to different agents.

Updated Apr 3, 2026

Search Tags:#agent coordination #escalation #rejection #review workflow #lockout #reassignment

Ready to run

npx skills add https://github.com/sachinnair90/gitgloss --skill reviewer-protocol-sachinnair90

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill reviewer-protocol-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents rejected work from looping back to the original author, enforcing independent revision ownership and avoiding biased self-fixes.

Core Features & Use Cases

Rejection lockout: Ensures the original author cannot revise the same rejected artifact.
Reassign or escalate: Lets a reviewer route the revision to a different agent or spawn a specialist when needed.
Deadlock-safe coordination: Handles repeated rejections and forces escalation when all eligible agents are locked out.
Use case: A tester rejects a feature implementation and the coordinator must assign a different engineer to produce the next version without involving the original author.

Quick Start

Use the reviewer-protocol skill to enforce reviewer rejection lockout and route 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 the original author from revising a rejected artifact in a code review workflow?▼

Reviewer rejection lockout prevents original authors from revising rejected artifacts. It enforces strict verification that the revision owner is not the original author, ensuring independent rework across coordinated review workflows and avoiding biased self-fixes.

What happens to a rejected work item when all eligible agents are locked out of the revision cycle?▼

When all eligible agents are locked out during repeated rejections, the workflow forces an escalation. This deadlock-safe coordination mechanism spawns a specialist or escalates the artifact when no independent agents remain available for rework.

How does reviewer reassignment work when a tester rejects a feature implementation?▼

Reviewer reassignment routes rejected artifacts to a different agent for independent revision. The coordinator assigns a new engineer to produce the next version, enforcing persistent per-artifact lockout so the original author cannot intervene.

Can I use rejection lockout to enforce independent revision ownership across multiple coordinated agents?▼

Yes, rejection lockout enforces independent revision ownership across coordinated review workflows. It applies to testers, code reviewers, or leads, maintaining persistent per-artifact lockout through each revision cycle to prevent biased self-fixes.

When do I need a rejection lockout protocol for agent coordination?▼

You need a rejection lockout protocol when coordinated review workflows require strict separation between artifact authors and revisers. It prevents rejected work from looping back to the original author, ensuring unbiased, independent revisions.