plugin-dev-setup

Manage symlink creation and environment configuration for KiCad ActionPlugin development.

3|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/plocher/jBOM --skill plugin-dev-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-dev-setup
Source: https://github.com/plocher/jBOM/tree/main/.agents/skills/plugin-dev-setup
Command: npx skills add https://github.com/plocher/jBOM --skill plugin-dev-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, and includes scripts (resource) components.

What problem does it solve?

This skill resolves the friction in developing KiCad ActionPlugins by managing the complex symlink requirements, sys.path bootstrapping, and garbage collection pitfalls that often break plugin functionality during local development.

Core Features & Use Cases

  • Development Loop Automation: Provides standardized commands to symlink plugin source code into KiCad's local environment for immediate testing.
  • Environment Guardrails: Documents critical constraints like the PCM identifier naming convention and SWIG/CPython garbage collection memory management.
  • Release Preparation: Includes workflows for building and validating PCM archives for distribution.

Quick Start

Execute the setup commands for your specific operating system to create a symlink between the jBOM plugin source directory and your local KiCad scripting plugins folder.

Frequently Asked Questions about plugin-dev-setup

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

FAQPage Schema
How do I set up a KiCad ActionPlugin for local development and testing?

To set up KiCad ActionPlugin development, this skill automates creating symlinks between your plugin source directory and KiCad's local scripting folder, enabling immediate smoke-testing within the PCB editor.

Why does my KiCad ActionPlugin fail to load due to Python path issues?

KiCad ActionPlugin loading fails without correct sys.path bootstrapping. This skill resolves this by managing the complex symlink requirements and enforcing proper Python environment configuration.

How do I package a KiCad plugin for PCM distribution?

To package a KiCad plugin for PCM distribution, this skill provides workflows for building and validating PCM archives, ensuring your ActionPlugin meets the required naming conventions for release preparation.

Can I use this skill to manage SWIG and CPython garbage collection issues in KiCad plugins?

This skill manages SWIG and CPython garbage collection pitfalls by enforcing proper object reference management, preventing memory leaks that often break ActionPlugin functionality during local development.

Do I need pytest installed to use this KiCad plugin development skill?

Yes, pytest is a required dependency. This skill leverages pytest to facilitate the testing phase of the KiCad ActionPlugin development loop, ensuring your plugin source modifications are validated.

What is the best way to streamline the KiCad ActionPlugin development loop?

The best way to streamline KiCad ActionPlugin development is by automating environment configuration and symlink creation, which this skill provides through standardized setup commands for your specific operating system.