skills.rest
acmeleme
acmelemeOFFICIAL
Explore all skills by this author →
GitHub

reviewer-protocol

Enforce reviewer-driven rejections with strict lockout and reassignment rules.

Updated Nov 11, 2025
Search Tags:#governance#review#code-review#escalation#lockout#reassignment
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill reviewer-protocol-acmeleme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill reviewer-protocol-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates governance around code review workflows by ensuring that rejected work cannot be revised by the original author, enforcing independent revisions and reducing feedback loops.

Core Features & Use Cases

  • Enforced lockout rules: The coordinator prevents the original author from producing the next revision.
  • Reassignment or escalation: On rejection, a different agent is assigned or escalated to handle the revision.
  • Governance and deadlock handling: The system validates reviewer recommendations and prevents deadlocks by escalating when needed.

Quick Start

Apply this skill to automatically route rework after rejection and ensure a different agent handles revisions.

Frequently Asked Questions about reviewer-protocol

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

FAQPage Schema
How do I enforce a code review lockout so the original author cannot revise rejected work?▼

To enforce a code review lockout, you need a coordinator that prevents the original author from producing the next revision. This skill automates that governance by blocking original authors and routing rework to different agents.

What is the best way to handle code review escalation and reassignment upon rejection?▼

Handling code review escalation upon rejection requires routing the work to a different agent. This skill automatically reassigns rejected artifacts to new agents or escalates them, ensuring independent revision and reducing feedback loops.

Can I use automated governance to prevent review deadlocks in artifact revision workflows?▼

You can use automated governance to prevent review deadlocks by validating reviewer recommendations and escalating when needed. This skill formalizes governance requirements and handles deadlock scenarios during artifact revisions.

How do you reassign a different agent after a code review rejection?▼

To reassign a different agent after a code review rejection, the system applies lockout semantics against the original author. This skill coordinates that reassignment by validating agent selection and routing the revision independently.

When do I need independent revision rules for code review governance?▼

You need independent revision rules when governance requirements mandate that rejected work cannot be revised by the original author. This skill applies strict lockout semantics to ensure revisions are handled independently across code reviews and artifact revisions.

Related Skills

Explore More Software Engineering Skills→
QuintenpsQuintenps

reviewer-protocol

Enforce reviewer lockout and reassign rejected artifacts to new agents.

Community
Advanced
christianhellechristianhelle
413

reviewer-protocol

Enforce rejection lockout and reassign artifact revisions to different agents.

Community
Advanced
ricablericable
1

Pair Programming

Facilitate AI-assisted pair programming with dynamic role management and automated verification.

Community
Advanced
ronniegeraghtyronniegeraghty
3

reviewer-protocol

Enforce reviewer-driven revision workflows with strict lockout and non-author assignment.

Community
Advanced