reviewer-common

Define common settings, modes, output formats, and scoring criteria for reviewer agents.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill reviewer-common
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer-common
Source: https://github.com/takemo101/compose-workflow/tree/main/.opencode/skill/reviewer-common
Command: npx skills add https://github.com/takemo101/compose-workflow --skill reviewer-common

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized framework and guidelines for various reviewer agents, ensuring consistent quality and scoring across different review types (design and implementation).

Core Features & Use Cases

  • Standardized Frontmatter: Defines common configurations for different reviewer personas (e.g., backend, frontend, design reviewers).
  • Mode Switching: Supports distinct modes for design review (based on documents) and implementation review (diff-driven).
  • Output Formatting: Enforces a uniform structure for review feedback, including scores, detailed evaluations, and action items.
  • Scoring Criteria: Establishes clear scoring rubrics and severity levels for feedback.
  • Use Case: Ensures that every code review, regardless of the reviewer's specialization, adheres to the same quality standards, uses the same scoring system, and provides actionable feedback in a predictable format.

Quick Start

Configure the reviewer-common skill to define the scoring criteria for all design reviewers.

Frequently Asked Questions about reviewer-common

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

FAQPage Schema
How do I standardize code review feedback across different roles like backend and frontend?

Standardize code review feedback by defining common frontmatter configurations, output formats, and scoring criteria for backend, frontend, database, security, and infra reviewer agents. This ensures consistent quality and actionable feedback across all specialized roles.

What is the best way to score design reviews consistently?

Score design reviews consistently by applying established scoring rubrics and severity levels for feedback. Define clear scoring thresholds and guidelines for different reviewer types to maintain uniform quality standards across all design documents.

How do I switch between design review and implementation review modes?

Switch between design and implementation review modes by toggling settings based on document inputs for design or diff-driven inputs for implementation. This mode switching ensures the review process targets the correct development phase.

Can I enforce a uniform output structure for code review scoring and action items?

Enforce a uniform output structure for code review scoring by specifying detailed output formats that include scores, evaluations, and action items. This standardizes feedback delivery regardless of the specific reviewer's specialization.

Do I need any dependencies to set up standardized quality assurance guidelines?

No dependencies are required to set up standardized quality assurance guidelines. The framework operates independently to define operating modes, feedback severity, and scoring thresholds for various reviewer personas.

What are the limitations of using a standardized framework for design and code reviews?

The framework is limited to defining settings, modes, and scoring criteria for reviewer agents. It standardizes the review process structure but does not perform the actual code or design analysis itself.