consolidate-reviews

Consolidating multiple code review files involves reading review documents matching a glob pattern, merging overlapping findings through de-duplication, highlighting reviewer disagreements, and outputting a structured triage table categorized by severity for efficient artifact review.

De-duplication in code review reporting merges similar findings from different reviewers into a single entry, reducing noise and redundancy. You need it when multiple engineers review the same artifact and their feedback documents contain overlapping issues that complicate triage.

Yes, you can surface disagreements in a consolidated report by merging review files and explicitly flagging where reviewers have conflicting opinions on severity or resolution. This structured triage output clearly categorizes these conflicts for immediate attention.

Use glob patterns like 'plans/reviews/requirements-review-*.md' to select input review files for consolidation. The skill reads all matching files, determines the artifact name from the filenames, and merges them into a single de-duplicated triage table.

Yes, code review consolidation works without external dependencies. The skill uses internal scripts and references to read review files, determine artifact names from filenames, and output a structured document for user triage without requiring additional packages.

The best way to triage redundant feedback is to consolidate the review files into a single de-duplicated table. This approach merges overlapping findings, categorizes them by severity (Critical, Warning, Suggestions, Positive), and surfaces disagreements for efficient decision-making.