triage

Group code review findings into Fix Now, Fix Later, and Skip categories.

3|Updated Oct 20, 2025

Search Tags:#code quality #code review #developer workflow #prioritization #action plan #triage

Ready to run

npx skills add https://github.com/mrstroz/claude-code-plugins --skill triage-mrstroz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/mrstroz/claude-code-plugins/tree/main/agent-teams-review/skills/triage
Command: npx skills add https://github.com/mrstroz/claude-code-plugins --skill triage-mrstroz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of acting on code review findings by intelligently triaging them into actionable groups, saving developers time and ensuring critical issues are addressed first.

Core Features & Use Cases

Smart Prioritization: Automatically categorizes findings into "Fix Now," "Fix Later," and "Skip."
Intelligent Grouping: Consolidates related findings into logical work packages for efficient handling.
Severity Verification: Re-evaluates reviewer-assigned severity against real-world impact.
Use Case: After a code review generates a long list of findings, use this Skill to get a clear, prioritized action plan, distinguishing between immediate must-fixes and deferrable improvements.

Quick Start

Use the triage skill to analyze the review report located at 'docs/reviews/my-review-report.md'.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I prioritize code review findings into an actionable developer workflow?▼

To prioritize code review findings, you can triage a review report into actionable groups like Fix Now, Fix Later, and Skip, assessing real impact, blast radius, effort, and regression risk to create a clear action plan.

What is the best way to group related code review findings for efficient fixing?▼

Grouping related code review findings uses smart grouping strategies like proximity, domain, pattern, dependency chaining, and effort bundling to consolidate related issues into logical work packages for efficient handling.

How do I create a code review action plan that distinguishes immediate must-fixes from deferrable improvements?▼

Creating a code review action plan involves categorizing findings by re-evaluating reviewer-assigned severity against real-world impact, separating immediate must-fixes from deferrable improvements based on actual blast radius and effort.

Do I need access to git logs and diffs to triage code review findings?▼

Yes, triaging code review findings requires access to git logs and diffs for context to accurately assess location, regression risk, dependencies, and the real impact of each finding.

Can I re-evaluate reviewer-assigned severity levels against real-world impact during code review triage?▼

Yes, severity verification re-evaluates reviewer-assigned severity against real-world impact, ensuring that the prioritization of findings into Fix Now, Fix Later, or Skip groups reflects actual blast radius and regression risk.