Files
Kill_LIFE/docs/KICAD_AI_LOCAL.md
Clément SAILLANT c2addfd81d feat(hw): add schops tool for schematic operations and kicad-cli integration
- Introduced `kicad_cli.sh` for local and Docker-based kicad-cli execution.
- Created `schops.py` for schematic operations including ERC, BOM, netlist exports, and bulk edits.
- Added README.md for schops with installation and usage instructions.
- Included requirements.txt for necessary Python packages.
- Implemented rules engine for applying field defaults and renaming nets.
- Added tests for rules engine functionality.
- Introduced scope guard script to enforce file modification policies based on PR labels.
- Created watch script to monitor KiCad files and trigger hardware gate on changes.
2026-02-18 23:47:56 +01:00

1.8 KiB
Raw Permalink Blame History

IA & KiCad en local (bulk edits + analyse)

Ce template privilégie deux couches complémentaires :

  1. schops (ce repo) : un CLI simple, traçable, qui fait

    • exports déterministes via kicad-cli (ERC / BOM / netlist)
    • bulk edits via kicad-sch-api (fields / footprints / labels)
    • packaging de Design Blocks KiCad 9
  2. MCP (optionnel) : si tu utilises un client IA compatible MCP, tu peux exposer des opérations KiCad comme un “tool server” local.

1) schops

Install :

python -m venv .venv && source .venv/bin/activate
pip install -r tools/hw/schops/requirements.txt

Workflow typique :

python tools/hw/schops/schops.py snapshot --schematic <...> --name before.json
python tools/hw/schops/schops.py apply-fields --schematic <...> --rules hardware/rules/fields.yaml
python tools/hw/schops/schops.py apply-footprints --schematic <...> --map hardware/rules/footprints.csv
python tools/hw/schops/schops.py rename-nets --schematic <...> --rules hardware/rules/nets_rename.yaml
python tools/hw/schops/schops.py erc --schematic <...>
python tools/hw/schops/schops.py bom --schematic <...> --exclude-dnp
python tools/hw/schops/schops.py netlist --schematic <...>
python tools/hw/schops/schops.py snapshot --schematic <...> --name after.json

Tous les rapports vont dans artifacts/hw/<timestamp>/.

2) MCP KiCad (optionnel)

Si ton client IA supporte MCP, installe un serveur MCP KiCad basé sur kicad-sch-api :

pip install kicad-sch-api kicad-sch-mcp

# démarre le serveur (stdio)
kicad-sch-mcp

Convention dintégration recommandée

  • Édits mécaniquesschops (backup + report)
  • Création de schéma / placement (si besoin) → MCP + validation ensuite via schops + kicad-cli

Même avec MCP, garde kicad-cli en “source de vérité” pour ERC/BOM/netlist.