skills.rest
barichter
barichterCOMMUNITY
Explore all skills by this author →
GitHub

reviewer-protocol

Enforce reviewer rejection workflows with strict lockout rules for independent revisions.

Updated Apr 12, 2026
Search Tags:#code review#software quality#team collaboration#independent review#reviewer lockout
One-click install
npx skills add https://github.com/barichter/squad --skill reviewer-protocol-barichter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/barichter/squad/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/barichter/squad --skill reviewer-protocol-barichter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that a reviewer's rejection of work by a team member does not allow the original author to self-revise, promoting independent reviews and maintaining code quality.

Core Features & Use Cases

  • Reviewer Rejection Protocol: Allows reviewers to approve or reject work, with options to reassign or escalate to a new agent.
  • Strict Lockout Semantics: Locks out the original author from revising the rejected artifact, ensuring independent revisions.
  • Use Case: When a code review is performed and the reviewer finds issues, they can reject the work, and the Skill ensures a different agent revises it.

Quick Start

Run the 'reviewer-protocol' skill with the command 'review work artifact'.

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 original author from self-revising code after a reviewer rejection?▼

To prevent original author self-revision after a reviewer rejection, you need a strict lockout protocol that blocks the author and requires an independent agent to handle the revisions.

What is a reviewer lockout protocol in software quality workflows?▼

A reviewer lockout protocol is a mechanism that enforces independent reviews by locking out the original author from revising rejected work, ensuring code quality through mandatory independent revisions.

How do I enforce an independent code review when a reviewer rejects an artifact?▼

You can enforce an independent code review by applying strict lockout semantics that reassign or escalate the rejected artifact to a new agent, preventing the original author from self-revising.

Can I reassign a rejected code review to a different agent using a lockout workflow?▼

Yes, the reviewer rejection workflow supports reassigning or escalating rejected work artifacts to a new agent, ensuring the original author is locked out and a different agent performs the revisions.

When do I need strict lockout rules for team collaboration and code reviews?▼

You need strict lockout rules for team collaboration when a reviewer rejects code and you must guarantee independent revisions, preventing the original author from bypassing the review process through self-revision.

Related Skills

Explore More Software Engineering Skills→
CommunityToolkitCommunityToolkit
619

reviewer-protocol

Enforce reviewer rejection workflows with strict lockout semantics for independent reviews.

Official
Advanced
lbouriezlbouriez

reviewer-protocol

Enforce reviewer rejection workflows with strict lockout of original authors.

Community
Advanced
mwathibenmwathiben

typescript-review

Review TypeScript and JavaScript diffs against Metabase coding standards.

Community
Intermediate
robinebersrobinebers
46

shepherd

Automate GitHub pull request review management until human approval.

Community
Advanced