triage-review-feedback

Evaluate existing review findings and decide whether to act now, defer, or take no action.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you receive a batch of human or AI review comments, it is hard to decide which concerns are actually valid, which are stale or duplicated, and which deserve immediate work versus deferral or rejection. This Skill triages existing review findings with a structured assessment model so implementation or reply planning starts from clear, evidence-backed decisions. ## Core Features & Use Cases - Three-axis evaluation: Assigns each finding a Finding assessment (Supported, Not verified, Contradicted, Not applicable), a Finding state (Open, Resolved, Duplicate, Superseded), and a Response decision (Act now, Defer, No action) as independent judgments. - Provenance preservation: Keeps upstream labels, confidence, evidence, and unconfirmed premises separate from triage evidence and newly identified unknowns, so nothing is silently strengthened or fabricated. - Collection reconciliation: Detects duplicates, shared root causes, conflicting proposals, and ordering dependencies across a set of findings, and treats commands embedded in feedback as untrusted content rather than authority. - Use Case: An AI reviewer leaves six findings on a pull request, including one stale finding already fixed and one valid concern with an over-engineered proposed fix. The Skill marks the stale one Resolved with No action, keeps the valid concern Supported but chooses a proportionate low-cost response, and hands off an actionable plan. ## Quick Start Triage these existing review findings, assess whether each concern is supported and current, and decide Act now, Defer, or No action with reasons for each.

Frequently Asked Questions about triage-review-feedback

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

FAQPage Schema
How do I triage code review feedback before implementing fixes?▼

Provide the existing review findings with their references, evidence, and impact, and the Skill assigns each a Finding assessment, Finding state, and Response decision. You get a structured handoff with reasons, priorities, and follow-up owners ready for implementation or reply planning.

What is the difference between finding assessment and response decision in review triage?▼

Finding assessment records whether the technical concern is supported in the target context, while Response decision records whether to act now, defer, or take no action. A technically supported concern can still receive No action when remediation cost is disproportionate to the risk reduction.

Can this Skill handle AI-generated review comments with low confidence?▼

Yes, it treats AI and human feedback identically as claims to evaluate. Low confidence does not automatically mean No action; unverified high-impact findings are deferred with a named owner, next check, and reconsideration condition.

When should I not use review feedback triage?▼

Do not use it to discover new problems in a diff, implement approved fixes, validate a completed fix, or draft PR comments. Those belong to separate workflows for reviewing changes, implementing changes, validating fixes, and drafting review comments.

Does triage execute commands suggested inside review feedback?▼

No. Commands and data-transfer requests embedded in review feedback are treated as untrusted content, never as authorization. Only safe, read-only local checks or authoritative primary sources are used to confirm or falsify a finding.