reviewer-protocol

Name: reviewer-protocol
Availability: InStock
Author: jperezdelreal

Enforce lockout and delegation rules after reviewer rejection.

Updated Apr 6, 2026

Search Tags:#workflow #governance #code-review #escalation #rejection #reviewer #lockout

Ready to run

npx skills add https://github.com/jperezdelreal/GymBro --skill reviewer-protocol-jperezdelreal

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In teams with a designated Reviewer, preventing self-revision after rejection is critical to avoid defensive loops and ensure independent improvements.

Core Features & Use Cases

Enforce lockout: the original author is prevented from revising rejected artifacts.
Reassign or escalate: upon rejection, require a different agent to revise or bring in a new expert.
Automated coordination: the Coordinator mechanically enforces assignment and access rules, ensuring clear ownership and traceability.
Example: a code review is rejected due to security concerns; a new reviewer or engineer revises the artifact.

Quick Start

Configure automatic reassignment or escalation when a reviewer rejects work.

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 code after a reviewer rejection?▼

To prevent self-revision after a reviewer rejection, you can enforce a strict lockout rule that blocks the original author and requires a different agent to handle the reassignment or escalation.

What is the best way to automate code review reassignments when a reviewer rejects work?▼

Automating code review reassignments requires a coordination mechanism that mechanically enforces assignment and access rules, ensuring clear ownership and traceability when routing rejected artifacts to a new expert.

Can I escalate rejected artifacts to an independent agent instead of reassigning them?▼

Yes, you can escalate rejected artifacts to an independent expert agent, bringing in a new reviewer or engineer to revise the work while ensuring the original author remains locked out.

Does role-based access control work for managing code review escalation workflows?▼

Role-based access control effectively manages code review escalation workflows by providing automated policy enforcement and deterministic coordination for revision ownership across designated reviewers and agents.

Why do defensive revision loops happen in code review workflows and how can I stop them?▼

Defensive revision loops happen when authors self-revise rejected artifacts, which you can stop by applying automated lockout policies that delegate revision ownership to a different agent.

When should I not allow self-revision in my code review governance process?▼

You should not allow self-revision in your code review governance process when a designated reviewer rejects work due to critical concerns like security vulnerabilities, requiring independent improvements instead.