review-workflow

Analyze code changes using a 5-category rubric with severity levels.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/IndianBoy42/dot-opencode --skill review-workflow-indianboy42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-workflow
Source: https://github.com/IndianBoy42/dot-opencode/tree/main/skills/review-workflow
Command: npx skills add https://github.com/IndianBoy42/dot-opencode --skill review-workflow-indianboy42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent code reviews across teams due to subjective judgments. This framework provides a clear 5-category rubric, a structured output format, and defined severity levels to ensure thorough, repeatable evaluations.

Core Features & Use Cases

  • 5-category evaluation: Style & Conventions, Bugs & Logic, Performance, Maintainability, Documentation.
  • Structured output: Consistent, machine-readable review summaries suitable for tooling and dashboards.
  • Severity levels: Clear triage of issues (Critical, Warning, Suggestion) to prioritize fixes.
  • Use Case: When reviewing diffs or PRs, apply this framework to produce a standardized assessment and actionable items.

Quick Start

Review the latest patch using the 5-category rubric to produce a structured evaluation.

Frequently Asked Questions about review-workflow

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

FAQPage Schema
How do I standardize code review quality across my team's pull requests?

Standardize code review quality by applying a 5-category rubric covering Style & Conventions, Bugs & Logic, Performance, Maintainability, and Documentation to produce consistent, structured pull request evaluations.

What is a structured code review rubric and how does it work?

A structured code review rubric evaluates diffs across five defined categories and assigns severity levels to issues. This enforces consistent, repeatable patch evaluations by replacing subjective judgments with objective quality criteria.

How do I categorize severity levels during a patch review?

Categorize severity levels during a patch review by assigning issues as Critical, Warning, or Suggestion. This severity triage prioritizes fixes and generates machine-readable output suitable for dashboards and tooling.

Does this code review framework work for diffs and patch reviews?

Yes, this code review framework works for diffs, patch reviews, and pull requests. It applies a consistent evaluation model across teams to ensure thorough quality and maintainability assessments for any code changes.

What's the best way to generate machine-readable code review summaries?

Generate machine-readable code review summaries by applying a structured rubric to analyze code changes. This produces standardized assessments with defined severity levels and frontmatter-driven discovery for easy tooling integration.