08 / 08 · What we check

A writeup you can actually hand to your team.

Every review ends with a structured report: an overall score, every finding categorized by severity, and enough detail that your team can act on it without a follow-up call.

01
Overall score. A single top-line number so you can track review quality across projects over time.
02
Severity-tagged findings. Every issue labeled Critical, Major, Minor, or Suggestion so you know what to fix first.
03
File & line references. Findings point to the exact module and location, not a vague category.
04
Plain-language explanations. Each finding explains why it matters, not just what rule was triggered.
05
Shareable format. A single document you can attach to a ticket, forward to a manager, or archive with the project.

Sample findingDetailed Report

Finding #14 in cdc_bridge.v : line 88
Severity: Critical
Category: Clock-Domain Crossing

Signal 'data_valid_a' crosses from clk_a to clk_b
without a synchronizer. Recommend a 2-flop
synchronizer or handshake protocol.

Sample finding entry as it appears in your reportCritical

Every finding in the report follows this format: location, severity, category, and a plain-language explanation with a recommendation.

Why it matters