review-triage

Convert batches of reviewer feedback into a structured per-finding decision table.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you respond consistently to reviewer feedback by turning a batch of comments into a structured decision table with a clear action for each finding.

Core Features & Use Cases

  • Per-finding triage: Converts every reviewer comment into its own row so nothing gets merged or missed.
  • Decision discipline: Forces each item into exactly one outcome: accept, push back, or defer.
  • Evidence-backed responses: Requires technical evidence for push-back, a fix summary for accept, and a follow-up reference for defer.
  • Review workflow support: Works for internal multi-reviewer phases as well as pasted feedback from GitHub PRs, Slack, or email.

Quick Start

Paste the review comments and ask the skill to respond to them with an accept, push-back, or defer decision for each finding.

Frequently Asked Questions about review-triage

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

FAQPage Schema
How do I triage code review comments from a pull request?

Triage pull request review comments by pasting them to generate a structured table mapping each finding to an accept, push-back, or defer decision with evidence.

What is the best way to handle multiple reviewer feedback in code review?

Handling multiple reviewer feedback involves converting every comment into its own row, ensuring nothing is missed by forcing exactly one accept, push-back, or defer outcome per finding.

Can I use Slack or email comments for review triage?

Yes, you can paste Slack or email comments directly to convert them into a structured per-finding response table with clear decisions and required evidence.

How do I document push-back on a code review finding?

Document push-back on a code review finding by providing required technical evidence backing your decision within the structured per-finding response table.

When should I defer a code review comment?

Defer a code review comment when immediate action is not possible, requiring a follow-up reference within the structured table to track the deferred finding.