code-review

Review local code changes for correctness, security, and production readiness.

88|15|Updated May 25, 2026
One-click install
npx skills add https://github.com/open-octo/octo-agent --skill code-review-open-octo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/code-review
Command: npx skills add https://github.com/open-octo/octo-agent --skill code-review-open-octo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces author bias and missed defects by coordinating a fresh, read-only review of local code changes.

Core Features & Use Cases

  • Isolated Analysis: Dispatches a sub-agent with no prior implementation context for an objective assessment.
  • Production Readiness Checks: Evaluates correctness, conventions, performance, tests, security, and technical design compliance.
  • API Contract Verification: Validates modified client structures against canonical upstream definitions and real JSON deserialization fixtures.
  • Use Case: When a feature branch is ready for review, use this Skill to inspect its diff, verify relevant design and API contracts, identify issues by severity, and produce a merge-readiness assessment.

Quick Start

Use the code-review skill to review the current branch against its main branch and report critical, important, and minor findings.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review local code changes for production readiness?

Review local code changes for production readiness by analyzing git diffs and source files to evaluate correctness, security, maintainability, and test coverage. This process identifies critical defects and generates a merge-readiness assessment for feature branches.

Can I verify API contract compliance using a git diff?

Verify API contract compliance using a git diff by validating modified client structures against canonical upstream definitions and real JSON deserialization fixtures. This ensures modified implementations align with technical design constraints and prevents contract violations.

How do I get an unbiased code review for a pull request?

Get an unbiased code review for a pull request by dispatching an isolated sub-agent with no prior implementation context to assess the diff. This fresh, read-only perspective reduces author bias and catches missed defects across multiple severity levels.

What does a production readiness check for a feature branch cover?

A production readiness check for a feature branch covers correctness, conventions, performance, tests, security, and technical design compliance. It inspects git diff context and relevant source files to categorize issues by severity for merge validation.

Do I need to provide test cases when running a security analysis on a bug fix?

Provide test cases that validate real boundary behavior when running a security analysis on a bug fix. Tests are required alongside git diff context and source files to accurately assess correctness and production readiness.

What is the best way to check technical design compliance for an API client change?

Check technical design compliance for an API client change by supplying git diff context, relevant source files, and canonical API contract evidence. This validates modified structures against upstream definitions and produces a merge-readiness assessment.