skills.rest
WayneWalterBerry
WayneWalterBerryCOMMUNITY
Explore all skills by this author →
GitHub

reviewer-protocol

Enforce reviewer rejection workflows with lockout rules preventing original author self-revision.

Updated Mar 19, 2026
Search Tags:#workflow#code-review#escalation#rejection#reviewer#lockout
One-click install
npx skills add https://github.com/WayneWalterBerry/MMO --skill reviewer-protocol-waynewalterberry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/WayneWalterBerry/MMO/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/WayneWalterBerry/MMO --skill reviewer-protocol-waynewalterberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rejection workflows in collaborative teams can lead to self-revision loops when the original author re-submits after a rejection. This Skill enforces a strict lockout policy and directs revisions to a different agent to preserve independent review.

Core Features & Use Cases

  • Enforces reviewer-based decisions (approve or reject) and applies a defined path when rejected (reassign or escalate).
  • Implements strict lockout: the original author is prevented from contributing the next revision; a non-author revision owner is selected by the Coordinator.
  • Prevents deadlock by validating reviewer instructions and providing escalation options for specialist needs.

Quick Start

Assign a reviewer to an artifact, and apply the rejection policy to ensure the original author is locked out and a new revision owner is chosen.

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 an artifact after a code review rejection?▼

A reviewer lockout workflow prevents the original author from submitting revisions after a rejection. It enforces a non-self-revision path by requiring the coordinator to select a different agent for the artifact revision.

What is a reviewer lockout workflow in artifact revision scenarios?▼

A reviewer lockout workflow is a policy-driven control for code review and QA validation. It locks out the original author after a rejection, enforcing a non-author revision path to preserve independent review integrity.

How do I enforce a non-author revision path when a reviewer rejects an artifact?▼

To enforce a non-author revision path upon rejection, apply a policy-driven control that directs the coordinator to reassign the artifact. This lockout rule strictly prevents the original author from contributing the next revision.

Can I escalate an artifact rejection for specialized expertise instead of reassigning it?▼

Yes, you can escalate an artifact rejection for specialized expertise. The rejection workflow validates reviewer instructions and provides escalation options to prevent deadlock while maintaining the strict author lockout.

Does the reviewer rejection workflow support both code review and QA validation processes?▼

Yes, the reviewer rejection workflow supports both code review and QA validation processes. The lockout policy applies to any artifact revision scenario requiring a different agent to revise or escalate after a rejection.

What happens if a reviewer provides invalid instructions during the rejection workflow?▼

If a reviewer provides invalid instructions, the rejection workflow prevents deadlock by validating the reviewer instructions. It ensures the coordinator can still select a non-author revision agent according to the review outcome.

Related Skills

Explore More Product & Management Skills→
quaid-appquaid-app
3

reviewer-protocol

Coordinate reviewer rejection workflows with enforced lockout rules preventing self-revision.

Official
Advanced
lbouriezlbouriez

reviewer-protocol

Enforce reviewer rejection workflows with strict lockout of original authors.

Community
Advanced
chdalychdaly

reviewer-protocol

Enforce reviewer rejection lockout rules and reassign revision authorship.

Community
Advanced
PlagueHOPlagueHO
2

reviewer-protocol

Enforce reviewer rejection workflows with strict lockout preventing self-revision.

Community
Advanced