reviewer-pack

Standardize review pipelines with configurable severity rubrics and repair-verification gates.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill reviewer-pack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer-pack
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/reviewer-pack
Command: npx skills add https://github.com/AesopScott/mojo --skill reviewer-pack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of standardized control in review queues, preventing accidental authority expansion and ensuring that changes to review logic are bounded, tested, and verified.

Core Features & Use Cases

  • Configurable Severity Rubric: Define what severity means within your specific context to ensure consistent prioritization.
  • Reviewer-Agent Sets: Implement custom plugins to determine who or what reviews specific findings.
  • Repair-Verification Gate: Enforce a mandatory proof-of-work requirement before any repair is accepted into the system.
  • Use Case: When modifying a review pipeline, use this skill to implement a new severity threshold and verify it with a positive and boundary test before deployment.

Quick Start

Invoke the reviewer-pack skill to initialize a new capability control plan for the Review Queue harness.

Frequently Asked Questions about reviewer-pack

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

FAQPage Schema
How do I enforce strict boundary control in an automated review pipeline?

To enforce strict boundary control in a review pipeline, apply configurable severity rubrics, reviewer-agent sets, and mandatory repair-verification gates to bound, test, and verify all logic changes.

What is a repair-verification gate in software engineering compliance?

A repair-verification gate is a mandatory proof-of-work requirement that enforces positive and boundary testing before any repair is accepted into a review system, ensuring auditability and preventing accidental authority expansion.

How do I standardize severity thresholds for a review queue harness?

Standardize severity thresholds for a review queue by implementing a configurable severity rubric that defines prioritization rules, ensuring consistent evaluation across automated and manual review processes.

Can I use custom reviewer-agent sets for specific findings in my pipeline?

Yes, you can implement custom reviewer-agent sets as plugins to determine exactly who or what reviews specific findings, providing precise control over your automated and manual review workflows.

Does this review pipeline approach require dependency setup or prior environment configuration?

No external dependencies are required to use this approach, allowing you to directly initialize a capability control plan for your review queue harness without prior environment configuration.

When should I not use automated severity rubrics for pipeline reviews?

You should avoid automated severity rubrics when your operational workflows lack defined safety protocols, as this approach requires strict adherence to safety protocols and verification of all changes through testing.