code-review

Reviews a git diff against coding standards and the originating spec using parallel sub-agents.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill code-review-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/code-review
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill code-review-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often conflate two separate questions — does the code follow the repo's standards, and does it implement what was actually asked for — letting one axis mask failures in the other. This Skill separates them into parallel sub-agent reviews over the diff between HEAD and a fixed point, then aggregates the findings side by side. ## Core Features & Use Cases - Two-axis review: A Standards axis checks the diff against documented repo standards plus a fixed baseline of Fowler code smells, while a Spec axis checks the diff against the originating issue or spec. - Parallel sub-agents: Both axes run as isolated sub-agents so their contexts do not pollute each other, and findings are reported separately without reranking. - Gate and tier integration: Reads the latest quality gate report and router tier to scope the review (full, sampling, or auto-skip) and avoid re-litigating metrics the gate already covers. - Use Case: Before merging a feature branch, ask for a review since the main branch; the Skill pins the merge-base diff, locates the linked issue, runs both reviews, and saves an aggregated report bound to the gate's source hash so the commit gate can verify it. ## Quick Start Ask the assistant to review the changes since main using the code-review skill and report standards and spec findings separately.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a branch against coding standards and its spec?

Provide a fixed point such as a commit SHA, tag, or branch name, and the Skill diffs it against HEAD using a three-dot merge-base comparison. It then runs two parallel sub-agents, one for standards and one for spec compliance, and aggregates their findings.

What happens if there is no spec or issue for the changes?

The Skill searches commit messages for issue references, checks user-supplied paths, and looks under docs, specs, or .scratch directories. If nothing is found and the user confirms no spec exists, the Spec sub-agent is skipped and the report notes that no spec was available.

Does the review duplicate what the quality gate already checks?

No. Findings a green gate already covers, such as coverage, mutation kill ratio, and complexity, are out of scope and cited once rather than re-litigated per hunk. Unavailable metrics and missing or stale reports are flagged explicitly instead.

What are the full, sampling, and auto review tiers?

The router tier scopes the review: full reviews every changed file, sampling reviews only the router's highest-risk sampled files, and auto skips the review entirely when the gate is credibly green. Sampling reports must state exactly how many files were reviewed.

Why are standards and spec findings reported separately?

A change can pass one axis and fail the other, such as standards-compliant code that implements the wrong thing. Keeping the axes separate and refusing to rerank findings prevents one axis from masking failures in the other.