Code Review

Structured pull request review. Focuses on issues introduced by this change, not pre-existing ones. Produces a prioritized HTML report.

When to Use

• Reviewing a PR before merge
• Reviewing your own code before opening a PR
• Security or correctness audit of a specific diff
• Reviewing code after implementing a feature (incremental review)

What NOT to Do

• Do not flag pre-existing issues the author didn't touch
• Do not block on style/formatting — that's what linters are for
• Do not rewrite code to a personal preference
• Do not list speculative risks without evidence