What problem does it solve? Deeply reviewing a large pull request or contribution requires understanding the whole system, not just the diff, and turning that analysis into a clear, actionable report is time-consuming and inconsistent. ## Core Features & Use Cases - Maintainer-Grade Review Workflow: Reconstructs the system design behind a PR, orders findings by severity, cites concrete file references, and separates architectural objections from product-scope concerns. - Polished Report Artifacts: Produces standalone HTML reports using a bundled starter template and editorial style guide, or Markdown reports, with sections for summary, tutorial, findings, comparisons, and recommendation. - Actionable Recommendations: Ends every review with a concrete call such as merge as-is, merge after redesign, salvage specific pieces, or keep as design research. - Use Case: A maintainer facing a 5,000-line plugin-system PR asks for a deep review and receives a navigable HTML report explaining the architecture, listing severity-ranked findings with file references, comparing the design to similar open-source systems, and recommending which parts to keep. ## Quick Start Review the current branch as a PR and produce a standalone HTML report with findings and a merge recommendation in tmp/reports.
