/re-report

description: Generate comprehensive reverse engineering analysis report
allowed-tools: Bash, Read, Write, Glob, Grep
argument-hint:

> **Storage Policy**: ALL output files MUST be saved in the project directory. NEVER write to `/tmp/` or any system temporary directory.

Generate Analysis Report

This command compiles all analysis data into a comprehensive markdown report.

Step 1 — Gather Data

node "${CLAUDE_PLUGIN_ROOT}/scripts/analysis-tracker.js" list
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list --db ioc
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show

Step 2 — Read Existing Reports

Check for existing analysis files in the project directory:

• `analysis-*.md`
• `secrets-*.md`
• `classify-*.md`
• `diff-*.md`
• `reports/*.md`

Step 3 — Compile Report

Generate `RE-REPORT-<date>.md` with:

# Reverse Engineering Report

**Date:** <date>
**Analyst:** Romero RE Plugin
**Session:** <session-number>

## Executive Summary
<2-3 sentence overview of all analysis performed>

## Binary Inventory
| Binary | SHA256 | Type | Classification |
|--------|--------|------|----------------|

## Analysis Coverage
| Binary | Phase | Status | Findings |
|--------|-------|--------|----------|

## Findings by Severity

### CRITICAL
<findings>

### HIGH
<findings>

### MEDIUM
<findings>

### LOW / INFO
<findings>

## Indicators of Compromise (IOCs)
| Type | Value | Binary | Severity |
|------|-------|--------|----------|

## Technique Coverage
| Analysis Type | Count | Results |
|---------------|-------|---------|

## Risk Assessment
<overall risk evaluation based on findings>

## Recommendations
<actionable next steps>

Step 4 — Save

Save report to `RE-REPORT-<date>.md` in the project directory.