review

Produce structured code reviews for diffs, PRs, or scoped paths.

9|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/harnessprotocol/harness-kit --skill review-harnessprotocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/harnessprotocol/harness-kit/tree/main/plugins/review/skills/review
Command: npx skills add https://github.com/harnessprotocol/harness-kit --skill review-harnessprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The review skill helps you quickly assess code changes by turning diffs into structured feedback that highlights what to fix before merge.

Core Features & Use Cases

  • Structured per-file review: Produces file-by-file feedback with severity labels (BLOCKER, WARNING, NIT) and line references where possible.
  • Cross-file analysis: Detects issues that span multiple files, such as missing test coverage, API contract changes, and dependency additions.
  • Overall decision guidance: Recommends an overall verdict such as Approve, Request Changes, or Questions based on the changeset.

Quick Start

Use the review skill to review your current branch changes by invoking /review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I get structured code review feedback for a local branch diff?

To get structured code review feedback, invoke the review skill against your local branch diff. It analyzes changes against a base branch like main, producing file-by-file feedback with severity labels and an overall merge verdict.

How do I check test coverage and API contract changes across multiple files?

To check test coverage and API contract changes, the review skill performs cross-file analysis on the changeset. It detects missing tests and contract modifications spanning multiple files, flagging them with severity labels for actionable feedback.

Can I review scoped path changes instead of an entire git diff?

Yes, you can review scoped path changes by using path-filter inputs. The skill restricts diff collection and analysis to those specific paths, applying the same structured severity labeling and overall decision guidance.

Does the code review output include severity labels for merge decisions?

Yes, the code review output includes severity labels such as BLOCKER, WARNING, and NIT for per-file issues. It recommends an overall merge verdict like Approve, Request Changes, or Questions based on the findings.