skills.rest
Izak90
Izak90COMMUNITY
Explore all skills by this author →
GitHub

reviewer-protocol

Enforce per-artifact lockout rules after reviewer rejection to reassign revisions.

Updated Nov 27, 2024
Search Tags:#workflow#review#code-review#escalation#artifact#coordinator#lockout
One-click install
npx skills add https://github.com/Izak90/Izak90.github.io --skill reviewer-protocol-izak90
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/Izak90/Izak90.github.io/tree/main/isaac_treinos_ar_livre/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/Izak90/Izak90.github.io --skill reviewer-protocol-izak90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rejection workflows must prevent the original author from self-revising and ensure a neutral, independent revision path through a lockout mechanism.

Core Features & Use Cases

  • Enforces per-artifact lockout when a reviewer rejects work, forcing a different agent to revise.
  • Supports reassign and escalate options to bring in the appropriate expertise.
  • Automates coordination checks to ensure the revision author is not the original author and prevents co-authoring during revision.

Quick Start

Submit an artifact for review, have it rejected, and let the system assign a non-original agent to produce the revision.

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

A lockout-driven reviewer workflow prevents original authors from self-revising rejected artifacts. By enforcing strict per-artifact lockout rules, it blocks the original author and forces a neutral, independent revision path by a different agent.

What happens during code review escalation when all eligible agents are locked out?▼

During code review escalation when all eligible agents are locked out, the system escalates to bring in a new expert. This ensures the collaborative development artifact can still be revised independently without violating the lockout rules against the original author.

How does a coordinator enforce revision author identity in a collaborative development workflow?▼

A coordinator enforces revision author identity by verifying the author of the new revision against the original artifact creator. It prevents co-authoring during the revision process and ensures the new revision is produced by a different, eligible agent.

Can I reassign a rejected artifact to a different agent instead of escalating?▼

Yes, you can reassign a rejected artifact to a different agent instead of escalating. The lockout-driven workflow supports reassign and escalate options to bring in the appropriate expertise for producing the independent revision.

What are the limitations of using per-artifact lockout scopes for code review?▼

A limitation of per-artifact lockout scopes is that if all eligible agents become locked out, the system must escalate to a new expert. Additionally, it strictly prevents co-authoring during revision, which may restrict collaborative fixing approaches.

Related Skills

Explore More Software Engineering Skills→
chdalychdaly

reviewer-protocol

Enforce reviewer rejection lockout rules and reassign revision authorship.

Community
Advanced
elbrunoelbruno
2

reviewer-protocol

Enforces reviewer rejection workflows with strict author lockout semantics in multi-agent orchestration.

Community
Intermediate
WizarckWizarck
2

doc-coauthoring

Guides structured co-authoring workflows for documentation, proposals, and technical specifications.

Community
Basic
PlagueHOPlagueHO
2

reviewer-protocol

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

Community
Advanced