Cast Review Vote

Cast ACCEPT or REVISE votes with written rationale in Aura workflows.

2|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/dayvidpham/aura-plugins --skill cast-review-vote
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Cast Review Vote
Source: https://github.com/dayvidpham/aura-plugins/tree/main/skills/reviewer-vote
Command: npx skills add https://github.com/dayvidpham/aura-plugins --skill cast-review-vote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Casts and records voting decisions for plans and code reviews to ensure consistent governance and traceability.

Core Features & Use Cases

  • ACCEPT and REVISE voting options with clear criteria for plan and code reviews.
  • Requires three reviewers for consensus and writes the rationale as a Beads comment for auditability.
  • Supports both plan reviews (Phase 4, s4-review) and code reviews (Phase 10, s10-review) within Aura workflows.

Quick Start

Cast an ACCEPT or REVISE vote on the active review and attach a concise justification in the Beads task.

Frequently Asked Questions about Cast Review Vote

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

FAQPage Schema
How do I cast a consensus vote on a code review with written rationale?▼

To cast a consensus vote on a code review, you submit an ACCEPT or REVISE decision alongside a concise written justification, which the system then records as a comment to ensure auditability and traceability.

What is the required number of reviewers to reach consensus in Aura workflows?▼

Consensus in Aura workflows requires three reviewers to cast votes. Each vote must include a written rationale and is posted as a Beads comment to maintain governance traceability.

How do I record an ACCEPT or REVISE decision for a plan review?▼

You record an ACCEPT or REVISE decision for a plan review by applying the vote during Phase 4 and attaching a written justification, which is then posted as a Beads comment for auditability.

Does the code review voting process enforce written rationale for every vote?▼

Yes, the code review voting process enforces that every ACCEPT or REVISE vote includes a written rationale to ensure governance, which is then posted as a Beads comment for traceability.

When do I need to use the REVISE voting option in a review workflow?▼

You use the REVISE voting option during plan or code reviews when changes are required before approval, ensuring your written rationale is posted as a Beads comment for the required three-reviewer consensus.

Can I use Beads comments to trace voting decisions across plan and code reviews?▼

Yes, you can use Beads comments to trace voting decisions, because the system posts every ACCEPT or REVISE vote with its written rationale as a comment for auditability in both plan and code reviews.