reviewer-vote

Record ACCEPT or REVISE votes with justifications in Beads tasks.

1|Updated Mar 10, 2026

Search Tags:#workflow #quality assurance #code review #beads #consensus #aura protocol

Ready to run

npx skills add https://github.com/dayvidpham/pasture --skill reviewer-vote

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewer-vote
Source: https://github.com/dayvidpham/pasture/tree/main/.opencode/skill/reviewer-vote
Command: npx skills add https://github.com/dayvidpham/pasture --skill reviewer-vote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, binary voting mechanism for plan and code reviews within the Aura Protocol, ensuring consistent consensus and clear audit trails.

Core Features & Use Cases

Binary Decision Making: Enforces a strict ACCEPT or REVISE vote to eliminate ambiguity in review phases.
Audit Integration: Automatically links votes to Beads tasks with required justifications and rationale.
Use Case: During a Phase 4 plan review or Phase 10 code review, use this skill to formally record your approval or request revisions based on established criteria.

Quick Start

Use the reviewer-vote skill to cast an ACCEPT vote on the current task by adding the appropriate justification comment to the Beads task tracker.

Frequently Asked Questions about reviewer-vote

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

FAQPage Schema

How do I record a binary vote for a code review in the Aura Protocol?▼

To record a binary code review vote in the Aura Protocol, use this Skill to cast an ACCEPT or REVISE decision and attach a mandatory justification comment to the Beads task tracker.

What is the difference between ACCEPT and REVISE votes in Beads task tracking?▼

ACCEPT and REVISE are the only two binary voting options in Beads task tracking, designed to eliminate ambiguity by requiring a strict decision alongside a mandatory rationale for phase-specific review criteria.

When do I need to cast a consensus vote during an Aura workflow?▼

You need to cast a consensus vote during Aura workflow Phase 4 plan reviews and Phase 10 code reviews to ensure task ratification meets established phase-specific compliance criteria.

Does the Aura Protocol require a justification comment for every review vote?▼

Yes, the Aura Protocol requires a mandatory justification comment for every review vote to maintain a clear audit trail linking the binary decision to the Beads task tracker.

Can I use this binary voting mechanism outside of the Beads task tracker?▼

No, this binary voting mechanism is specifically designed to integrate with the Beads task tracker to manage recording and ensure compliance within the Aura Protocol workflow engine.

What are the limitations of binary voting for plan reviews?▼

Binary voting limits decisions to ACCEPT or REVISE, restricting nuanced feedback but enforcing clarity, and requires mandatory justification comments to prevent unexplained rejections during consensus building.