Repo Report Builder

Goal

Produce a business-readable, technically grounded report from repository source code. Generate the final report from scratch for the specific repos and findings; do not reuse a fixed report template.

Default output is a multi-page static HTML report with local CSS/JS. Mermaid diagrams are expected, and using a Mermaid CDN renderer is acceptable unless the user requires fully offline output.

Operating Principles

• Treat repository code as evidence. If a question can be answered by inspecting code, inspect code instead of asking the user.
• Ask one question at a time only for decisions that cannot be discovered from the repos.
• Keep business readers in mind: explain behavior, risk, and decisions clearly, with expandable technical evidence for engineers.
• Ask explicitly about sensitivity/redaction before building. Do not silently choose a redaction policy.
• Prefer GitHub links pinned to the analyzed commit SHA when repos are hosted on GitHub. Fall back to repo-relative or local file references for non-GitHub repos.
• Use risk severity ratings when discussing bugs, security weaknesses, operational risks, or code quality issues.
• Include full rebuild recommendations where they make sense; otherwise recommend refactor, stabilize, retire, or keep.
• Do not mutate source repos unless the user explicitly asks. Report generation may create files in the requested output directory.