schematic-analyzer

KiCad schematic analysis identifies core components, nets, and subsystems from raw netlists and maps bus patterns to real hardware, enabling precise architecture reviews and BSP bring-up. It transforms raw designs into structured, evidence-backed understanding of topology.

Yes, pattern detection for buses and interfaces runs at runtime against KiCad schematics. It supports hierarchical sheets and MCP overlays to locate shared buses and verify which devices participate in them to identify design risks.

Yes, structured schematic analysis requires both python3 and kicad-cli installed. Every inference is grounded in CLI output from overview, query, or pattern results, escalating to datasheet or MCP only when necessary to answer a specific claim.

Running CLI-driven queries against a KiCad project returns compact JSON suitable for downstream tooling. These queries cover overview, page, component, net, and pattern results to provide an architecture-aware view of power rails and subsystem boundaries.

Yes, schematic analysis supports hierarchical sheets in KiCad projects. It provides page-context to locate main controllers and subsystem boundaries, ensuring structured analysis covers the full design architecture across all hierarchical levels.

You should escalate to datasheet or MCP during KiCad schematic analysis only when CLI output from overview, query, or pattern results is insufficient to answer a specific claim. Every inference must otherwise be directly grounded in CLI-driven evidence.