skills.rest
mpaulosky
mpauloskyCOMMUNITY
Explore all skills by this author →
GitHub

reviewer-protocol

Enforce reviewer rejection workflows that lock out the original author from revising.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines a structured workflow where a Reviewer can approve or reject work, and the original author is prevented from making the next revision after a rejection, ensuring independent, unbiased reconsideration.

Core Features & Use Cases

  • Enforces strict lockout semantics after a rejection to prevent self-revisions by the original author.
  • Supports two revision paths: Reassign to a different agent or Escalate to a new expert, based on Reviewer feedback.
  • Provides guardrails for deadlock handling, escalation, and programmatic coordination by a Coordinator.

Quick Start

Apply reviewer-protocol to enforce no-self-revise policy and automatically route revisions to a different agent when a rejection occurs.

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 rejection?▼

To prevent self-revision after a code review rejection, you need a lockout policy that blocks the original author and automatically routes the work to a different agent for independent revision.

What is a reviewer-driven code review workflow?▼

A reviewer-driven code review workflow is a governance process where a designated Reviewer approves or rejects artifacts and controls revision routing, ensuring unbiased corrections by enforcing independent reassignment or escalation.

How do I handle a deadlock when a revision agent is unavailable during code review?▼

Handling a deadlock during code review requires an escalation protocol that detects when reassignment fails and automatically escalates the rejected artifact to the user or a new expert for resolution.

Can I reassign rejected work to a specific revision agent instead of escalating?▼

Yes, you can reassign rejected work to a specific different agent. The reviewer protocol supports two revision paths: direct reassignment to another agent or escalation to a new expert based on feedback.

What are the limitations of enforcing strict reviewer lockouts in a development workflow?▼

Strict reviewer lockouts limit the original author's autonomy entirely and can create bottlenecks if no alternative revision agents are available, requiring deadlock escalation to the user to resolve.

Related Skills

Explore More Software Engineering Skills→
quaid-appquaid-app
3

reviewer-protocol

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

Official
Advanced
rm-rf-etcrm-rf-etc

openspec-continue-change

Create the next artifact in an OpenSpec change workflow.

Community
Advanced
4lerman4lerman

ci-cd-pipeline-builder

Detect repository stacks and generate CI/CD pipeline templates for GitHub Actions and GitLab CI.

Community
Advanced
robpitcherrobpitcher

reviewer-protocol

Enforce reviewer-based rejection workflows that lock out original authors from revising.

Community
Advanced