opencode-review

Automate iterative code review with OpenCode and Claude before commits.

5|1|Updated Oct 18, 2019
One-click install
npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill opencode-review-marshall-hallenbeck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-review
Source: https://github.com/Marshall-Hallenbeck/dot_files/tree/main/.claude/skills/opencode-review
Command: npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill opencode-review-marshall-hallenbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires opencode.

What problem does it solve?

This skill addresses the inconsistency of single-model code reviews by implementing a rigorous, iterative dual-review process that ensures code is vetted by both OpenCode and Claude before it is committed.

Core Features & Use Cases

  • Dual-Model Validation: Combines the strengths of OpenCode (MiniMax M2.5) and Claude to catch bugs, logic errors, and style issues.
  • Iterative Refinement: Automatically enforces a loop that continues until both reviewers report a clean status, ensuring high-quality output.
  • Use Case: Use this before committing complex features to ensure that security vulnerabilities, logic gaps, and style inconsistencies are caught and resolved by two distinct AI perspectives.

Quick Start

Run the opencode_review command to initiate the iterative review process on your current uncommitted changes.

Frequently Asked Questions about opencode-review

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

FAQPage Schema
How do I automate code review for security vulnerabilities and style violations before a git commit?

An iterative dual-review pipeline automates code review by running uncommitted changes through both OpenCode and Claude to catch bugs, security issues, and style violations before a git commit.

What is a dual-model code review pipeline and how does it improve software quality assurance?

A dual-model code review pipeline combines OpenCode and Claude to iteratively validate source code. It enforces a refinement loop until both models report a clean status, catching bugs and style violations that a single model might miss.

Do I need the OpenCode CLI tool installed to run an automated iterative code review?

Yes, you need the OpenCode CLI tool installed and accessible in your system path. The pipeline relies on the OpenCode CLI for external model invocation to successfully execute the dual-review validation process.

How do I start an iterative code review process on my uncommitted changes?

To start an iterative code review on uncommitted changes, run the review command to trigger the automated pipeline. The system applies both OpenCode and Claude to your current working changes, looping until all detected issues are resolved.

When should I use a dual-model AI review instead of a single-model code review?

Use a dual-model AI review when committing complex features that require high-assurance code quality. The dual-review process addresses single-model inconsistency by ensuring code is thoroughly vetted by two distinct AI perspectives.

What happens if OpenCode or Claude finds bugs during the iterative code review loop?

If OpenCode or Claude finds bugs during the iterative review loop, the pipeline automatically enforces a refinement cycle. This loop continues until both reviewers report a clean status, ensuring all security issues and logic gaps are fully resolved.