skills.rest
dayvidpham
dayvidphamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reviewer-comment

Standardize review findings with severity classification via Beads CLI.

1|Updated Mar 10, 2026
Search Tags:#workflow#feedback#audit#beads#review#code-review
One-click install
npx skills add https://github.com/dayvidpham/pasture --skill reviewer-comment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-comment
Source: https://github.com/dayvidpham/pasture/tree/main/.opencode/skill/reviewer-comment
Command: npx skills add https://github.com/dayvidpham/pasture --skill reviewer-comment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of consistency in review feedback by enforcing a structured format for plan and code reviews, ensuring that findings are categorized by severity and tracked effectively.

Core Features & Use Cases

  • Structured Feedback: Enforces a clear VOTE (ACCEPT/REVISE) and severity-based findings (BLOCKER, IMPORTANT, MINOR).
  • Beads Integration: Directly interfaces with the Beads CLI to log comments into the project's permanent record.
  • Use Case: During a Phase 10 code review, use this skill to categorize a security vulnerability as a BLOCKER and a naming suggestion as a MINOR issue, ensuring both are captured in the audit trail.

Quick Start

Use the reviewer-comment skill to add a structured review comment to task ID 123 with a REVISE vote and a list of identified blocker issues.

Frequently Asked Questions about reviewer-comment

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

FAQPage Schema
How do I standardize code review feedback for an audit trail?▼

You can standardize code review feedback by enforcing a structured format with ACCEPT or REVISE votes and severity-based findings like BLOCKER or MINOR to maintain a consistent project audit trail.

What is the best way to categorize review findings by severity in phase-based task management?▼

Categorizing review findings by severity involves classifying issues as BLOCKER, IMPORTANT, or MINOR. This structured feedback ensures critical vulnerabilities are prioritized during phase-based code reviews.

How do I log structured review comments into a permanent project record?▼

You log structured review comments into a permanent project record by integrating with the Beads CLI, which executes comment creation and maintains consistency across project reviews.

Does the Aura Protocol require the Beads CLI for code review workflows?▼

Yes, standardizing documentation of review findings within the Aura Protocol requires integration with the Beads CLI to execute comment creation and maintain consistency across project reviews.

When do I need to use a REVISE vote for code review findings?▼

Use a REVISE vote during code review when you identify issues that require changes before approval. This vote is paired with categorized findings like BLOCKER or MINOR issues to document necessary revisions.

Related Skills

Explore More Software Engineering Skills→
dayvidphamdayvidpham
1

architect-ratify

Validate reviewer consensus and update proposal metadata via the pasture CLI.

Community
Intermediate
limit5limit5

SKILL_HD_LIFECYCLE_AUDIT

Conduct standardized annual reproducibility audits for HD lifecycle processes.

Community
Intermediate
channingwaltonchanningwalton
3

Code Reviewer

Automate code review across files, diffs, and repositories with severity-ranked findings.

Community
Basic
dayvidphamdayvidpham
1

worker-complete

Validate quality gates and update task status in the Beads system.

Community
Advanced