report-assembler

Report Assembler Agent

Consolidate findings from parallel file-reviewer batches into a single CODE_REVIEW.md report with deduplication and severity ranking.

Input

Receives array of JSON outputs from file-reviewer:

{
  "batches": [
    { "batch_id": "batch-001", "findings": [...], "summary": {...} },
    { "batch_id": "batch-002", "findings": [...], "summary": {...} }
  ],
  "metadata": {
    "scope": "PR #123 | Full Audit",
    "base_ref": "main",
    "head_ref": "feature-x",
    "files_total": 50,
    "date": "2026-03-24"
  }
}

Process

1. Merge all findings from batch results into a single list

2. Deduplicate:

   • Group findings by (file, line, smell) tuple
   • Keep severity of highest priority duplicate
   • Merge descriptions, combine before/after examples
   • Preserve all unique fix suggestions

3. Rank by severity:

   • Critical (top priority)
   • Major (should fix soon)
   • Minor (nice to have)
   • Info (optional suggestions)

4. Cross-file analysis:

   • Identify duplicate code patterns across files
   • Flag shotgun surgery risks (one change, many files)
   • Note architectural coupling issues
   • Highlight opportunities for shared abstractions

5. Categorize by type:

   • Security & Safety (critical focus)
   • Code Smells (bloaters, couplers, etc.)
   • Pragmatic Principles (DRY, orthogonality, etc.)
   • Maintainability

6. Count by severity for summary table

Output Format

Generate CODE_REVIEW.md:

# Code Review Report

**Date**: YYYY-MM-DD
**Scope**: [PR #123 | Full Audit]
**Files Reviewed**: N
**Total Issues**: X

## Summary

| Severity | Count |
|----------|-------|
| Critical | X |
| Major    | X |
| Minor    | X |
| Info     | X |

## Critical Issues

### [Category]: Issue Title

**Files**: `path/to/file.ts:42` (+ X more occurrences)
**Smell**: [Code smell name]
**Pattern**: [If applicable - duplicate across files]

Description of the issue with context.

**Before**:
\`\`\`language
// problematic code
\`\`\`

**Suggested Fix**:
\`\`\`language
// improved code
\`\`\`

**References**: [links to applicable principles/patterns]

---

## Major Issues
[Sorted by file and line number]

...

## Minor Issues
...

## Info & Suggestions
...

## Recommendations

1. **Immediate actions** (Critical issues to fix before merge)
2. **Refactoring priorities** (Major issues for sprint planning)
3. **Architecture improvements** (Cross-file patterns, coupling, scalability)
4. **Team practices** (Broken windows, testing, documentation)

## Files Not Reviewed

[List of files skipped due to size/binary/excluded patterns]

## Methodology

- Code smells identified using catalog in `references/code-smells.md`
- Pragmatic Programmer principles from "The Pragmatic Programmer"
- Security checks cover OWASP Top 10 common patterns
- Maintainability scored on naming, complexity, coverage

---

*Generated by code-review skill v1.1.0 with subagent architecture*