Claude Agent

finding-triage

Imported from arbiterforge/codearbiter/site/src/curated/agents/finding-triage.md.

LLM Mart · 0 points · 15 0 0

Download arbiterForge-codeArbiter-site_src_curated_agents_finding-triage.md-6039d39.zip · 0 KB

arbiterforge/codearbiter 145 7 forks AGPL-3.0 Updated 7d ago

Part of arbiterforge/codearbiter — 238 skills

Install

skills CLI npx skills add https://github.com/arbiterForge/codeArbiter/tree/main/site/src/curated/agents/finding-triage.md

Git git clone https://github.com/arbiterForge/codeArbiter.git

The skills CLI installs just this skill, for any of its supported agents. Git is the plain clone.

Files (codearbiter)

finding-triage.md 1.1 KB

---
entity: agents/finding-triage
related: [skills/dispatching-parallel-agents, verdict-aggregator, checkpoint-aggregator]
---

## Role

Post-processes every reviewer report from a checkpoint or review run: consolidates all findings and
classifies each as BLOCKS, DEFERRABLE, or NON_BLOCKING. It generates no findings of its own — it
unifies and classifies what the reviewer fleet already found. Runs sequentially after every reviewer
in the batch has reported, dispatched by `dispatching-parallel-agents`, and hands its complete report
to the read-only `verdict-aggregator`.

## Why this model tier

Ships `model: haiku`. Classifying an already-produced finding by severity and blocking status against
a fixed rule set is mechanical triage, not open-ended judgment.

## What it emits

A single unified triage report: one table row per finding under BLOCKS / DEFERRABLE / NON_BLOCKING,
with source reviewer, severity, description, and disposition, plus summary counts. Nothing is dropped
— every finding from every reviewer must appear. The report stays in memory; only an explicit
checkpoint flow may later persist the verdict through `checkpoint-aggregator`.