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

reviewer-review-code

Categorize code review findings into BLOCKER, IMPORTANT, and MINOR severity groups.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the lack of consistency and rigor in code reviews by enforcing a structured, EAGER severity-based workflow that ensures all issues are categorized and addressed before a code slice can be approved.

Core Features & Use Cases

  • EAGER Severity Tree: Automatically enforces the creation of BLOCKER, IMPORTANT, and MINOR severity groups for every review round to prevent oversight.
  • Quality Gate Enforcement: Integrates project-specific quality gates and production code path verification to ensure high-quality deliverables.
  • Clean-Review Exit: Manages review-fix-re-review cycles within a defined budget, ensuring no code is merged with outstanding findings.

Quick Start

Initiate the review process for a specific code slice by running the review-code skill against the target slice ID and URD context.

Frequently Asked Questions about reviewer-review-code

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

FAQPage Schema
How do I enforce consistent severity levels during a code review?▼

Code review severity levels are enforced using an EAGER severity tree that automatically creates BLOCKER, IMPORTANT, and MINOR groups. This structured categorization prevents oversight and ensures all issues are addressed before approval.

What's the best way to automate quality gate checks for production code paths?▼

Quality gate checks for production code paths are automated by integrating project-specific gates into the review workflow. This verifies compliance and ensures high-quality deliverables before a code slice is approved.

How do I manage review and fix cycles within a defined effort budget?▼

Review and fix cycles are managed within a defined effort budget using a clean-review exit process. This ensures no code is merged with outstanding findings and all review rounds stay constrained.

Does structured code review require explicit validation of test fixtures?▼

Structured code review requires explicit validation of test fixtures for all requests. This verifies the implementation phase meets production code path requirements and quality gate compliance.

When do I need to use an EAGER severity tree for workflow automation?▼

An EAGER severity tree is needed for workflow automation when you must enforce the creation of BLOCKER, IMPORTANT, and MINOR severity groups for every review round to prevent oversight.

Related Skills

Explore More Software Engineering Skills→
ArvorCoArvorCo
96

constitution

Create or update a project constitution defining coding principles and governance rules.

Community
Advanced
josephneumannjosephneumann
4

milestone-review

Review and fix Git branch issues iteratively with parallel AI reviewers.

Community
Advanced
chieflatifchieflatif
2

vibeos-gate

Run automated quality gates for VibeOS code across workflow phases.

Community
Intermediate
gaia-reactgaia-react
21

file-tech-debt

Create deduplicated GitHub issues for out-of-scope code findings with provenance tracking.

Official
Advanced