akcli-circuit-debuglisted

Systematically diagnose misbehaving schematics and `akcli` tool failures — no Altium or KiCad install required. Use this skill whenever the task involves: debugging net connectivity (a net that is split, merged wrongly, missing, or a pin that floats when it should not); triaging `akcli check` findings (real fault vs false positive, deciding whether a clean pass is trustworthy); investigating why `akcli plan`/`akcli draw` refused to write or what an exit code means; recovering from a failed apply (backup/rollback); or classifying parse failures and unsupported-input refusals before reporting a bug upstream. Triggers on keywords: debug, diagnose, troubleshoot, net split, floating pin, wrong net merge, false positive, ERC finding, exit code, parse error, refused, dangling endpoint, connectivity gate, rollback, backup, corrupt SchDoc, unsupported format.
tipoLi5890/akcli · ★ 4 · Code & Development · score 74

Install: claude install-skill tipoLi5890/akcli

# akcli-circuit-debug — systematic diagnosis with `akcli` Use this skill to find out **why** a schematic or `akcli` itself misbehaves. For basic read/analyze/draw mechanics (input formats, op-list authoring, config, the full workflow) see the **akcli-circuit-design** skill — this skill only covers diagnosis. Run every command with the `Bash` tool; from a raw checkout use `PYTHONPATH=src python3 -m akcli ...` or `bin/akcli ...`. Two ground rules: - **stdout is data, stderr is diagnosis.** `akcli ... --json | jq` stays clean; the not-found notices and `ERROR: CODE: ...` lines live on stderr. Capture both streams when debugging. - **Reproduce from raw data before theorizing.** Dump the net, dump the component, compare against the expectation — never argue from a rendered summary alone. ## Symptom → first command | Symptom | First command | |---|---| | Net looks split / pin floating / wrong merge | `akcli net <file> <NETNAME>` | | One component wired wrongly | `akcli component <file> <REF>` | | "Is this check finding real?" | `akcli check <file> --exit-zero --json` | | Two revisions disagree | `akcli diff <a> <b> --exit-zero` | | MCU pin assignment suspect | `akcli pinmap <file> --mcu U3` | | `draw`/`plan` refused to write | `akcli draw <target> --ops <ops.json>` (dry-run, read connectivity block) | | File will not parse at all | `akcli read <file> --debug` | | Unclear tool state | `akcli --version` (prints package **and** protocol version) | | Write refused by `TARGET_LO