GitPLM now supports KiCad HTTP API
This is now the preferred way to connect KiCad to the GitPLM library:
The GitPLM parts library now has a Claude Skill to add new parts
It seems to be working pretty well!
Video of the above feature:
This is looking really interesting Cliff ~ I’m still investigating how to tie in IPN’s with English language project names - src directories etc. Fantastic documentation on the IPN principle. Have release working but use a hook to kick off a Ruby script rather than use the bash stuff. Might need to dust off my Go (I used it once for a video project, and it was great). 
1 Like
In terms of Kicad and project reproducability , traceability, etc it is exactly the problem I am faced with. Hopefully I can contribute in some way going forward.
1 Like
I’ve found myself wishing there was a ‘post-bom generation’ hook for doing things like generating a human friendly bom etc. The current hook appears to run after release directory generation but prior to BOM generation. Or perhaps I should be adding another layer to the release (ASY) to enable that? At any rate I’m finding the GitPLM methodology very well thought out, and useful, and I would say makes working with Kicad (footprints, symbols etc) much nicer
In the v0.10.0 release.
I really like the interactive BOM, which is generated from the PCB file. I’ve added some examples for generating that.