Inspecting and checking
validate
Report document invariants that no longer hold.
Usage
validateAngle brackets mark required arguments and square brackets optional ones. Available in the schematic editor. You can issue this yourself, and the AI agent issues the identical command — there is no second, hidden interface.
Behaviour
Checks the sheet against the topology rather than against itself. Today it reports STALE JUNCTIONS: a dot left behind after the wires that justified it moved or were deleted, which still asserts a connection that is not there. KiCad deletes these silently on every edit; this reports them, because a document rewritten underneath a caller that holds handles is worse than one that tells you what is wrong. A clean sheet says so — an empty report is an answer, not a failure.
How the agent uses it
- The agent works in a perceive / act / verify / recover loop: it describes the design, issues
validateor another command, checks the result, and undoes the change if the check fails. - Commands report what they actually did. A refusal is a result, not a silent no-op — which is what lets the agent recover instead of building on a change that never happened.
- Anything the agent can do here, you can do yourself, and the reverse.
Other inspecting and checking
Try validate in the editor
Free to start on macOS, Windows and Linux. Bring your existing KiCad and Altium libraries.
