code-review

Automate structured code reviews evaluating architecture, quality, tests, and performance.

14|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/opencodos/opencodos --skill code-review-opencodos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/opencodos/opencodos/tree/main/skills/Code%20Review
Command: npx skills add https://github.com/opencodos/opencodos --skill code-review-opencodos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently review code changes with structured, opinionated guidance that surfaces tradeoffs and actionable recommendations.

Core Features & Use Cases

  • Structured review prompts covering architecture, code quality, tests, and performance
  • Tradeoff-focused feedback that clarifies risks and suggested directions
  • Interactive, decision-driven workflow to align stakeholders before changes

Quick Start

Ask the assistant to perform an interactive code review on your current changes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate an opinionated code review for my pull request?

To automate an opinionated code review for your pull request, initiate an interactive review session with your current changes. The assistant evaluates architecture, code quality, tests, and performance while prompting for decisions before applying recommendations.

What is a tradeoff-focused code review and how does it work?

A tradeoff-focused code review evaluates code changes by explicitly surfacing architectural risks and performance tradeoffs. It clarifies suggested directions and provides structured, actionable recommendations rather than just identifying syntax issues.

Can I use this structured code review process on an existing codebase?

Yes, you can use this structured code review process on an existing codebase. It applies to projects of varying sizes and languages, evaluating architecture, code quality, tests, and performance across the entire project.

Does the code review workflow require manual input before making architectural decisions?

Yes, the code review workflow requires manual input before making architectural decisions. It implements an interactive, decision-driven workflow with input prompts to align stakeholders before changes are applied.

What is the best way to evaluate code quality and performance tradeoffs during a review?

The best way to evaluate code quality and performance tradeoffs during a review is using structured review prompts. This approach clarifies risks across architecture and tests, providing explicit recommendations and actionable feedback.