drc-audit

Analyze KiCad DRC JSON reports to classify electrical and layout violations.

2|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/pjcau/esp32-emu-turbo --skill drc-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drc-audit
Source: https://github.com/pjcau/esp32-emu-turbo/tree/main/.claude/skills/drc-audit
Command: npx skills add https://github.com/pjcau/esp32-emu-turbo --skill drc-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Full KiCad DRC audit that detects shorts, unconnected pads, dangling vias, and clearance violations that are not caught by custom scripts, ensuring electrical integrity and manufacturability.

Core Features & Use Cases

  • Comprehensive KiCad DRC coverage that includes shorting, unconnected nets, via dangling, and various clearance/silk/copper interactions.
  • Automated analysis of KiCad DRC JSON output to classify violations, identify root causes such as pad-net assignment gaps, and propose fixes.
  • Actionable reports and remediation guidance used during PCB validation and production readiness.

Quick Start

Run KiCad DRC on your board and review the resulting JSON report to identify and fix violations.

Frequently Asked Questions about drc-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit KiCad DRC JSON reports for electrical violations?

To audit KiCad DRC JSON reports, you process the output file to detect shorts, unconnected pads, dangling vias, and clearance violations. This structured analysis classifies violations and provides root-cause recommendations to guide fixes.

What's the best way to find unconnected pads and shorts missed by custom scripts?

A full KiCad DRC audit analyzes the JSON output to identify shorts, unconnected nets, and via dangling issues that custom scripts miss. It classifies these electrical violations and pinpoints root causes like pad-net assignment gaps.

Does this DRC audit require a specific KiCad file format to work?

Yes, the audit relies on the KiCad DRC JSON report format. It applies to boards containing KiCad PCB files and parses the JSON output to surface clearance problems and silk or copper interactions.

How do I classify KiCad DRC violations and identify their root causes?

To classify KiCad DRC violations, you analyze the DRC JSON report to categorize shorts, unconnected items, and clearance problems. The audit identifies root causes such as pad-net assignment gaps and proposes actionable fixes.

Can I use a KiCad DRC audit for PCB production readiness checks?

Yes, a KiCad DRC audit is used during PCB validation and production readiness. It detects layout and electrical violations, producing actionable reports and remediation guidance to ensure hardware reliability.

Why does my custom script miss dangling vias and clearance problems in KiCad?

Custom scripts often lack comprehensive DRC coverage for via dangling and copper interactions. A full KiCad DRC audit applies the native JSON report to surface these missed clearance problems and classify electrical violations.