review-response

Triage GitHub PR review comments by severity and apply approved fixes.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dimakis/mitzo --skill review-response-dimakis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-response
Source: https://github.com/dimakis/mitzo/tree/main/skills/review-response
Command: npx skills add https://github.com/dimakis/mitzo --skill review-response-dimakis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered PR review comments into a systematic investigation plan, so issues are correctly understood and fixed instead of superficially addressed.

Core Features & Use Cases

  • Review-comment triage for PRs: Fetches review comments and pull-request inline comments for a specified PR number or the current branch’s open PR.
  • Evidence-driven investigation and classification: Reads the referenced code, searches for related patterns, and classifies each finding as Critical, Valid, or Cosmetic based on impact.
  • Fix-first workflow with approval gate: Presents findings in a compact table for review approval, then fixes everything marked for action while applying the Boy Scout rule.
  • Action-oriented escalation: If a finding implies a deeper underlying root cause, it fixes the root cause rather than patching symptoms.

Quick Start

Ask the AI to run review-response for PR 123 to triage every review and inline comment, investigate the underlying causes, classify severity, present a decision table, then fix everything approved.

Frequently Asked Questions about review-response

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

FAQPage Schema
How do I triage GitHub pull request review comments systematically?

Triage pull request review comments by fetching PR reviews and inline comments via gh, contextualizing them in the codebase, and classifying each finding by severity into a compact table for approval before fixing. This ensures issues are correctly understood and fixed at the root cause rather than superficially patched.

What is the best way to fix code review findings based on severity?

Fixing code review findings based on severity involves investigating each referenced code pattern, classifying impact as Critical, Valid, or Cosmetic, presenting a decision table for approval, and then applying evidence-based fixes that prioritize root-cause corrections over symptom patches.

Can I use gh CLI to fetch and categorize PR review comments automatically?

Yes, you can use gh to retrieve PR reviews and inline comments for a specified PR number or the current branch's open PR. The fetched comments are then read in codebase context, searched for related patterns, and categorized by severity before remediation is applied.

How do I investigate the root cause of issues found in a GitHub PR review?

Investigating the root cause of PR review issues requires reading the referenced code, searching for related patterns across the repository, and escalating action-oriented fixes that address the deeper underlying root cause rather than patching the visible symptoms.

Does this code review triage workflow require manual approval before applying fixes?

Yes, the code review triage workflow requires a manual approval gate. It presents all investigated findings in a compact table for your review, and only fixes items marked for action after approval while applying the Boy Scout rule to leave the codebase cleaner.