mentor-report-htmllisted

# mentor-report-html Turn a system or codebase into **one self-contained interactive HTML file** that a mentor, reviewer, or teammate can open by double-clicking — no server, no dependencies, no network. The report has two linked views over the *same* node/edge data: 1. **Flowchart** — modules / steps / code units laid out in columns (by `layer`), with directed edges showing how work flows through the system. 2. **Knowledge graph** — the same nodes in a force-directed layout; click any node to **highlight all of its relationships** (neighbours lit, everything else dimmed) so the reviewer instantly sees what a unit touches. Clicking a node also opens a **detail panel**: file path, one-line purpose, the key functions/classes in that unit, and a clickable list of its incoming/outgoing relationships. ## Files in this skill ``` mentor-report-html/ ├── SKILL.md (this file) ├── README.md / README.zh-CN.md └── templates/ ├── report_template.html self-contained report (light bg · Georgia · SVG/JS) └── data_example.json the node/edge schema, filled with a sample ``` ## How to build a report (agent workflow) **Goal:** produce a finished `report.html` describing the user's actual system. You do this by (a) extracting the structure from their code, then (b) filling the template's data block. ### 1. Scope it Ask (or infer) what the report should cover: a whole service, one subsystem, one request path, one pipeline. Keep it to s