fixme-handle-code-review

Classify code-review findings using a unified taxonomy after automated post-execution reviews.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/denis-pingin/fixme --skill fixme-handle-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixme-handle-code-review
Source: https://github.com/denis-pingin/fixme/tree/main/.claude/skills/fixme-handle-code-review
Command: npx skills add https://github.com/denis-pingin/fixme --skill fixme-handle-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and triage code review findings from a post-execution review. Classify each finding using the unified taxonomy (FIX, FIX_UNCLEAR, ASK_USER, REJECT_FALSE_POSITIVE, REJECT_WONT_FIX, REJECT_ALREADY_FIXED). Reads the plan, spec, implementation, and tests to distinguish real issues from false positives caused by misunderstood context, intent, or approach. Designed to eliminate harmful, incorrect, or context-blind feedback before it reaches implementation.

Core Features & Use Cases

  • Classifies each finding using a unified taxonomy: FIX, FIX_UNCLEAR, ASK_USER, REJECT_FALSE_POSITIVE, REJECT_WONT_FIX, REJECT_ALREADY_FIXED
  • Reads the plan, spec, implementation, and tests to distinguish real issues from false positives caused by context or assumptions
  • Supports decision logging and clear handoffs to execution phases

Quick Start

Scan the latest findings and classify each one using the taxonomy.

Frequently Asked Questions about fixme-handle-code-review

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

FAQPage Schema
How do I triage automated code review findings to filter out false positives?

Triage automated code review findings by reading the plan, spec, implementation, and tests to validate context, then classify each issue using a unified taxonomy to filter out false positives before execution.

What is the unified taxonomy for classifying code review defects?

The unified taxonomy for classifying code review defects includes FIX, FIX_UNCLEAR, ASK_USER, REJECT_FALSE_POSITIVE, REJECT_WONT_FIX, and REJECT_ALREADY_FIXED to determine accurate next steps for each finding.

How do I validate post-execution code review feedback against project specifications?

Validate post-execution code review feedback by cross-referencing findings against the plan, spec, implementation, and tests to ensure the feedback is accurate, safe, and actionable before it reaches implementation.

Can I use automated defect classification to stop context-blind code review comments?

Yes, automated defect classification eliminates harmful, incorrect, or context-blind code review comments by distinguishing real issues from false positives caused by misunderstood intent or approach.

What are the limitations of relying on automated code review triage?

Automated code review triage requires complete plan, spec, implementation, and test documentation to function accurately; missing context may limit its ability to distinguish real issues from false positives.

Does code review triage support decision logging for handoffs to execution phases?

Yes, code review triage supports decision logging and clear handoffs to execution phases by applying the unified taxonomy to classify issues and determine safe next steps.