tribunal

Run three-perspective adversarial reviews on code changes and plans.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/sr-ai-dev/sr-harness --skill tribunal-sr-ai-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tribunal
Source: https://github.com/sr-ai-dev/sr-harness/tree/main/skills/tribunal
Command: npx skills add https://github.com/sr-ai-dev/sr-harness --skill tribunal-sr-ai-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The tribunal skill helps you catch hidden risks, missing value, and feasibility gaps before you commit code or changes.

Core Features & Use Cases

  • Multi-perspective adversarial review: Runs three distinct panels—risk, value, and feasibility—to surface blind spots.
  • Verdict with structured scoring: Produces an APPROVE / REVISE / REJECT decision using a risk–value–feasibility matrix.
  • Actionable required changes: Extracts must-fix, should-address, and consider items based on panel findings.
  • Works for plans, PRs, and diffs: Reviews a local plan file, a GitHub PR, or current uncommitted changes via diff.

Quick Start

Run /tribunal with the path to your PLAN.md to receive a three-panel verdict and concrete revision actions.

Frequently Asked Questions about tribunal

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

FAQPage Schema
How do I perform an adversarial code review before merging a pull request?

An adversarial code review evaluates a pull request across risk, value, and feasibility dimensions to surface blind spots. This Skill runs three distinct analysis panels in parallel to produce a structured Tribunal Verdict with a scored decision matrix.

Can I assess the feasibility and risk of a local code diff before committing?

Yes, you can assess local uncommitted changes by running an adversarial analysis on your current diff. The review extracts must-fix items and evaluates feasibility gaps to help you decide whether to proceed, revise, or reject the changes.

What is a risk-value-feasibility matrix for evaluating a development plan?

A risk-value-feasibility matrix is a structured scoring method that evaluates a development plan from three adversarial perspectives. It synthesizes findings into an APPROVE, REVISE, or REJECT verdict, extracting actionable required changes based on panel findings.

Does this adversarial PR review work with GitHub pull requests?

Yes, this adversarial PR review works with GitHub pull requests, local plan files, and local diffs. It applies parallel risk, value, and feasibility analyses to the specified target to generate a final verdict with concrete revision actions.

How do I get actionable required changes from a code review verdict?

To get actionable required changes from a code review verdict, the analysis categorizes findings into must-fix, should-address, and consider items. When the verdict is REVISE or REJECT, it provides specific required actions based on the synthesized panel findings.

When should I use a multi-perspective adversarial review instead of a standard check?

Use a multi-perspective adversarial review when risk, value, and feasibility must be rigorously assessed before proceeding with a code change or plan. It surfaces hidden gaps and blind spots that a standard review might miss by running three independent analysis panels.