AI Reviewing AI: Why Our Multi-Agent PR Tribunal Is the Only Way We Survived the Diff Explosion

┌────────────────────────┐
                          │ Pull Request Opened │
                          └───────────┬────────────┘
                                      │
              ┌───────────────────────┼───────────────────────┐
              ▼ ▼ ▼
    ┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
    │ Security Agent │ │ Performance Agent│ │ Architecture/API │
    └─────────┬────────┘ └─────────┬────────┘ └─────────┬────────┘
              │ │ │
              └───────────────────────┼───────────────────────┘
                                      │
                                      ▼
                        ┌───────────────────────────┐
                        │ Dynamic Verification Agent│
                        │ (Runs Executable AST) │
                        └─────────────┬─────────────┘
                                      │
                                      ▼
                        ┌───────────────────────────┐
                        │ Consensus Engine │
                        └─────────────┬─────────────┘
                                      │
                   ┌──────────────────┴──────────────────┐
                   ▼ ▼
      [Unanimous Pass / Minor] [Blocking Disagreement]
                   │ │
                   ▼ ▼
        Surfaced to Human Review Blocked & Routed Back
         (With Audit Summary) To Author Agent

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "agentPersona": { "type": "string" },
    "verdict": { "type": "string", "enum": ["APPROVE", "REQUEST_CHANGES", "NEEDS_HUMAN_ELEVATION"] },
    "confidenceScore": { "type": "number", "minimum": 0.0, "maximum": 1.0 },
    "findings": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "filePath": { "type": "string" },
          "lineRange": { "type": "string" },
          "severity": { "type": "string", "enum": ["CRITICAL", "MAJOR", "MINOR"] },
          "ruleId": { "type": "string" },
          "description": { "type": "string" },
          "suggestedFix": { "type": "string" }
        },
        "required": ["filePath", "lineRange", "severity", "ruleId", "description"]
      }
    }
  },
  "required": ["agentPersona", "verdict", "confidenceScore", "findings"]
}

You are an uncompromising Performance & Systems Engineer auditing a Pull Request diff.
Your ONLY goal is to reject code that introduces runtime bottlenecks, memory leaks, or unoptimized I/O.

RULES:
1. Do NOT compliment the author or comment on code style.
2. Search for N+1 ORM queries, unindexed queries, blocking event loops, and missing connection pools.
3. If a loop contains an `await` call to an external network service, you MUST flag it as CRITICAL unless wrapped in batch concurrency primitives.
4. Output MUST strictly match `.github/tribunal/schemas/review-output.schema.json`.

// scripts/tribunal-consensus.ts
import * as fs from "fs";
import * as path from "path";

interface Finding {
  filePath: string;
  lineRange: string;
  severity: "CRITICAL" | "MAJOR" | "MINOR";
  ruleId: string;
  description: string;
  suggestedFix?: string;
}

interface ReviewOutput {
  agentPersona: string;
  verdict: "APPROVE" | "REQUEST_CHANGES" | "NEEDS_HUMAN_ELEVATION";
  confidenceScore: number;
  findings: Finding[];
}

function evaluateConsensus(resultsDir: string) {
  const files = fs.readdirSync(resultsDir).filter(f => f.endsWith(".json"));
  const reviews: ReviewOutput[] = files.map(f => 
    JSON.parse(fs.readFileSync(path.join(resultsDir, f), "utf-8"))
  );

  let hasCritical = false;
  let blockReasons: string[] = [];
  let totalFindings = 0;

  for (const review of reviews) {
    console.log(`[Tribunal] Processing ${review.agentPersona}... Verdict: ${review.verdict} (Confidence: ${review.confidenceScore})`);

    for (const finding of review.findings) {
      totalFindings++;
      if (finding.severity === "CRITICAL") {
        hasCritical = true;
        blockReasons.push(`❌ [${review.agentPersona}] ${finding.filePath}:${finding.lineRange} - ${finding.description}`);
      }
    }
  }

  if (hasCritical) {
    console.error("\n🚨 PR BLOCKED BY TRIBUNAL CONSENSUS ENGINE");
    blockReasons.forEach(reason => console.error(reason));
    process.exit(1);
  }

  console.log(`\n✅ PR Approved by Tribunal (${reviews.length} agents, ${totalFindings} non-critical findings). Routing to Human Reviewer.`);
}

evaluateConsensus(process.argv[2] || "./tribunal-results");

# 1. Trigger the Parallel Agent Reviewers on PR #412
$ npx tribunal-cli audit --pr 412 --out-dir ./tribunal-results

[Agent: Security] Analyzing 6 modified files...
[Agent: Performance] Analyzing 6 modified files...
[Agent: API-Compatibility] Analyzing 6 modified files...

[Agent: Security] Complete. Verdict: REQUEST_CHANGES (1 Critical, 0 Minor)
[Agent: Performance] Complete. Verdict: APPROVE (0 Critical, 2 Minor)
[Agent: API-Compatibility] Complete. Verdict: APPROVE (0 Critical, 0 Minor)

# 2. Run the Consensus Engine against the outputs
$ npx ts-node scripts/tribunal-consensus.ts ./tribunal-results

[Tribunal] Processing Security Audit Agent... Verdict: REQUEST_CHANGES (Confidence: 0.94)
[Tribunal] Processing Performance Agent... Verdict: APPROVE (Confidence: 0.89)
[Tribunal] Processing API Compatibility Agent... Verdict: APPROVE (Confidence: 0.98)

🚨 PR BLOCKED BY TRIBUNAL CONSENSUS ENGINE
❌ [Security Audit Agent] src/modules/user/service.ts:L42-L48 - Unsanitized input passed directly to raw SQL query execution. Potential SQL Injection.

# 3. Post summary comment to GitHub PR and reject merge gate
$ gh pr comment 412 --body-file ./tribunal-results/summary.md
$ gh pr edit 412 --add-label "tribunal/changes-requested"

### 💡 Need High-Impact Technical Content for Your Engineering Team?

I partner with developer-tooling startups, SaaS platforms, and engineering teams to translate complex infrastructure, agentic systems, and backend architecture into publication-grade technical writing.

Whether you need deep-dive architecture essays, hands-on developer tutorials, or technical counter-narratives:

📩 Email: abhishekninja2018@gmail.com

💼 LinkedIn: linkedin.com/in/abhishekninja

🐦 X (Twitter): @AvishekBanzzov

✍️ Medium: medium.com/@abhishekninja2018

💻 Dev.to: dev.to/abhishekninja_writer

🛠️ Capabilities: Long-form Technical Essays | Hands-On Tutorials | Developer Tooling Deep-Dives | Technical Counter-Narratives