jBOM

jBOM project git workflow — feature branches, semantic conventional commits, and the iterative pre-commit pattern required by this repository. Use when staging changes, committing, pushing, or creating PRs in this repository.

Resolves a GitHub issue either in the current agent session or by launching a child agent, while enforcing collaborative checkpoints and the jBOM git workflow. Use when the user provides an issue number and asks to assign/resolve it with /collaborative mode and /git-workflow, optionally choosing a model for a child agent.

Structures collaborative agent-user problem solving with adaptive tone, explicit status reporting, decision checkpoints, and shared understanding before execution continues. Use when the user requests collaborative-mode, says "collaborative mode", wants interactive brainstorming on alternatives, or invokes /collaborative.

Use when writing or reviewing behave/Gherkin scenarios for jBOM — covering the review checklist, colon-consistency rule, step parameterization patterns, annotated examples, and the dynamic test-data builder pattern that must be applied to every scenario in the jBOM BDD suite.

Procedural solution for configuring behave to load step definitions from subdirectory packages. Use when organizing behave step definitions into domain-specific subdirectories and encountering "Undefined step" errors, or when setting up a new subdirectory-based step structure for a behave feature suite.

Setting up a fresh jBOM development environment — clone, virtualenv, editable install, pre-commit hooks, running tests, common development tasks, and building distribution packages. Use when onboarding to jBOM development for the first time or when reinstalling a dev environment from scratch.

Use when adding a new jBOM CLI command, domain service, inventory file format, package type, component classifier, output column preset, or fabricator profile. Covers registration patterns, service skeletons, extension points in common/ and services/, and required testing steps. Also applicable when an agent needs to understand stable extension contracts vs. internal implementation details.

zsh-safe gh CLI patterns for authoring GitHub issue bodies, PR descriptions, and comments. Use when the body content contains shell-quoting hazards — backticks, exclamation marks, dollar signs, backslashes, or multi-line Markdown — that cause literal \n or mangled text when passed inline to gh via a quoted string.

Manually register a development version of kicad_jbom_plugin.py with KiCad's Eeschema "Tools → Generate BOM → Add plugin" dialog so the developer can test code changes without re-packaging or re-publishing through KiCad's Plugin and Content Manager (PCM). End users should install jBOM via PCM (see docs/reference/kicad-plugin.md#plugin-installation) rather than following this skill.

Set up the jBOM KiCad ActionPlugin development loop for contributors working on src/jbom/plugin/. Use when creating or recreating the dev symlink, activating the plugin in KiCad's Pcbnew, building the PCM archive for smoke-testing, or understanding the sys.path bootstrap and the KiCad SWIG/CPython GC gotcha.