triage-feedback

Clusters, dedupes, and routes multi-reviewer feedback findings for an artifact.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/mikestopcontinues/agent-skills --skill triage-feedback-mikestopcontinues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-feedback
Source: https://github.com/mikestopcontinues/agent-skills/tree/main/claude/skills/triage-feedback
Command: npx skills add https://github.com/mikestopcontinues/agent-skills --skill triage-feedback-mikestopcontinues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple reviewers each produce a findings file (rNN-{focus}.md) for the same artifact, the raw feedback overlaps, disagrees on severity, and mixes actionable defects with design opinions. This Skill consolidates that scattered review output into a single deduplicated, severity-normalized cluster list with an explicit routing decision for every cluster. ## Core Features & Use Cases - Cross-reviewer deduplication: Merges findings that name the same defect at the same location, taking the higher severity on disagreement and recording every contributing focus. - Topic clustering with severity normalization: Groups findings by decision, file region, or contract, and assigns each cluster the max severity of its members. - Deterministic routing: Marks ambiguity, blocking status, and decision-shape per cluster, then routes each to act, auto-act, process, lock-decisions, or defer — including a security-focus filter that drops nit/minor security findings. - Use Case: After three reviewers produce r01-accuracy.md, r03-dx.md, and r04-integration.md on a design document, run this Skill to collapse their findings into one cluster list showing that the auth-flow contract issues merge into a single Major, ambiguous, blocking cluster routed to process. ## Quick Start Triage all review files in the current artifact directory and return the routed cluster list for iteration 2.

Frequently Asked Questions about triage-feedback

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

FAQPage Schema
How do I combine feedback from multiple reviewers into one list?▼

Pass the list of review file paths (or the artifact directory containing r*.md files) to this Skill. It reads every finding, dedupes identical defects across reviewers, clusters them by topic, and returns one routed cluster list as conversational markdown.

How are duplicate findings across reviewers handled?▼

Two findings are duplicates when they name the same defect at the same location, even if worded differently. They merge into one cluster member recording every reviewer's focus, and on severity disagreement the merged member takes the higher severity — never an average.

What routing options exist for triaged feedback clusters?▼

Each cluster routes to act, auto-act, process, lock-decisions, or defer based on severity, ambiguity, and decision-shape. Blockers always route to act, nits to defer, and decision-shaped findings to lock-decisions regardless of severity.

Does the triage process re-evaluate reviewer severity ratings?▼

No. Severities are read from the H3 section each finding sits under and are never re-judged from opinion. The only exception is correcting a severity when the finding's stated rationale cites a fact verifiably wrong from the artifact itself.

What happens to minor security findings during triage?▼

Per the d08 security filter, nit and minor findings from the security focus are dropped entirely and counted in the output. Major and blocker security findings route to auto-act if unambiguous, or to the captain as blocking if ambiguous.