feedback-triage

Walk through code review findings or Azure DevOps PR threads and lock in Fix, Do Not Fix, or Defer outcomes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Review feedback often arrives as a long list of findings or PR threads with no clear decision on each item. This Skill walks you through every item one at a time, forcing a locked-in outcome of Fix, Do Not Fix, or Defer, and ends with a summary table so nothing is left ambiguous. ## Core Features & Use Cases - Dual source support: Triage findings from a /code-review run (grouped by high/medium/low severity, skipping info) or open threads on an Azure DevOps pull request. - Structured one-at-a-time walkthrough: Each item gets a recommended outcome, a fuller explanation, discussion time, and an agreed resolution before moving on. - Decision recording without side effects: Outcomes and rationale are logged to a temp scratchpad; the Skill never edits code, replies to threads, or changes thread status. - Use Case: After a code review produces 15 findings, run the triage to decide each one's fate in a single session, then hand the final summary table to whoever implements the fixes. ## Quick Start Ask the assistant to triage the review findings from the last code review, or say triage the PR and provide the Azure DevOps pull request link.

Frequently Asked Questions about feedback-triage

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

FAQPage Schema
How do I triage code review findings one at a time?

Run the triage on findings already in the conversation from a code review, or point to a saved review document. Each finding is presented with a recommended Fix, Do Not Fix, or Defer outcome, discussed, then locked in before moving to the next.

How do I walk through Azure DevOps PR review threads?

Provide the PR link or ID and the Skill pulls every open thread with full comment history, authors, and file context. Threads already marked Fixed, Closed, or Won't Fix are skipped, and each remaining thread is triaged in PR order.

Does triaging PR threads change their status or reply to them?

No. The triage only records decisions in a temp scratchpad and a final summary table. It never edits code, replies to threads, changes thread status, or creates tickets; those actions happen as a separate later step.

What happens to info-level findings during review triage?

Info-severity findings are dropped silently before triage begins. Only high, medium, and low findings are walked through, in that severity order, so the session focuses on items that need a real decision.

When should I mark review feedback as Do Not Fix?

Use Do Not Fix when the feedback turns out to be incorrect or not applicable after discussion. The rationale is captured in the scratchpad and summary table, since the reasoning behind rejecting feedback is the part worth keeping.