audit_find_inconsistent_track_widths
Detect nets with track-width ratios above 2× and flag thin orphan stubs; returns each net’s min/max widths and coordinates of its thinnest segment.
Instructions
Find nets where the maximum and minimum track widths differ by more than 2×.
Classic bug pattern: a power rail (VCC / VDD / GND) is routed at 20 mil to handle the expected current, then later someone adds a connection using the editor's default 8 mil width and moves on. The result is a thin orphan stub welded to a wide bus -- under load that thin section becomes a thermal hotspot and eventually a fab rework. Most agents and human reviewers miss it because the bulk of the net looks fine.
Algorithm: per net, collect min/max track widths on signal layers. Ratio > 2.0 → flag. Per-violation reports the actual widths and the (x, y) of the thinnest track on the net so the agent can jump straight to the questionable section.
Pattern: SDK-derived. No community-script reference.
Returns:
Dict with {checked, violations, items[]} where each
item carries {net, min_width_mils, max_width_mils, ratio, thin_x_mils, thin_y_mils}.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||