arbiter

Review code diffs holistically across correctness, edge cases, and patterns.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/benediktms/overmind --skill arbiter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arbiter
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/arbiter
Command: npx skills add https://github.com/benediktms/overmind --skill arbiter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates software changes holistically across correctness, edge cases, patterns, naming, contracts, and obvious code smells to catch issues that don't fit a single specialized lens.

Core Features & Use Cases

  • Holistic evaluation across correctness, edge cases, naming, and contract clarity.
  • Diff hygiene & best practices: detect unrelated changes, debug noise, and formatting issues.
  • API clarity & contracts: ensure explicit inputs/outputs and clear naming.
  • Decision guidance: provide ranked findings with severity and concrete remediations.

Quick Start

Review the given code changes as if you are a senior staff engineer and return prioritized findings with brief remediation steps.

Frequently Asked Questions about arbiter

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

FAQPage Schema
How do I perform a holistic code review on recent changes?

Holistic code review evaluates software diffs across correctness, edge cases, patterns, and naming. It acts as a senior staff engineer to catch issues missed by specialized lenses, returning prioritized findings with concrete remediation steps.

What issues does a holistic code review catch that specialized lenses miss?

Holistic code review catches obvious code smells, debug noise, and unclear API contracts that do not clearly fit under security, performance, testing, or style lenses. It evaluates changes across multiple quality dimensions to find gaps.

How do I check code diffs for unclear API contracts and naming?

Reviewing code diffs for API clarity ensures explicit inputs and outputs alongside clear naming conventions. The evaluation detects contract ambiguities and formatting issues, ranking them by severity with actionable remediation guidance.

When should I use a general code review instead of specialized security or performance tools?

Use a general code review when no specialized lens clearly covers the issue in your project changes. It evaluates diff hygiene, unrelated changes, and contract clarity to catch general quality issues across the entire codebase.

Does this code review approach work with any project's code diffs?

Yes, this code review approach applies to code diffs in any project. It evaluates changes across correctness, edge cases, patterns, naming, and code smells without requiring project-specific configurations or dependencies.

How are code review findings prioritized and formatted?

Code review findings are returned as a ranked list with assigned severity levels and brief remediation steps. This decision guidance helps teams address the most critical correctness and contract issues first.