Creates and configures IOC apps and modules with Bazel build system and runtime startup behavior.
npx skills add https://github.com/BCDA-APS/opencode-skills --skill epics-module
Please help me install this Agent Skill. Skill: epics-module Source: https://github.com/BCDA-APS/opencode-skills/tree/main/epics-module Command: npx skills add https://github.com/BCDA-APS/opencode-skills --skill epics-module
It removes uncertainty and rework when creating EPICS IOC applications and support modules by giving a correct, repeatable build and startup structure.
_registerRecordDeviceDriver.cpp is generated rather than edited.dbLoadDatabase, registration, record/template loads, and iocInit so IOCs start reliably.configure/RELEASE, update src/Makefile DBD fragments and library link order, and keep $(EPICS_BASE_IOC_LIBS) last.Ask the AI to generate a complete EPICS module layout for a new IOC named myApp with a support library named mySupport, including the correct Makefile variables, DBD fragment wiring, and an st.cmd that loads myRecords.db using the right startup command order.
High-intent search queries and answers about installing and using this skill.
To create an EPICS IOC application with makeBaseApp.pl, you must follow the two-step pattern to scaffold the ioc and support module directory trees, generating the correct configure/ and Makefile boilerplate for a repeatable build structure.
The correct st.cmd command order requires dbLoadDatabase and record-device-driver registration to execute before dbLoadRecords and iocInit, ensuring the EPICS IOC starts reliably and loads databases in the proper sequence.
To assemble DBD fragments for an EPICS IOC, combine base and support-module fragments in your src/Makefile, ensuring the _registerRecordDeviceDriver.cpp file is generated by the build system rather than edited manually.
EPICS IOC linking fails when dependent modules are not added via configure/RELEASE or when libraries are not linked in reverse dependency order, so you must always keep $(EPICS_BASE_IOC_LIBS) last in the src/Makefile.
You configure PROD_IOC, PROD_HOST, and LIBRARY_IOC appropriately in the EPICS Makefile to define build targets, matching composite DBD fragments to the PROD_IOC and linking required support libraries correctly.
Yes, you can use makeBaseApp.pl templates to scaffold both support modules and IOC directory trees, generating the complete EPICS build-system structure with proper configure/ files, Makefile variables, and startup behavior.
BioKTAutomate GROMACS source installation with PLUMED patching and CUDA/MPI configuration.
BCDA-APSAssemble, build, and initialize EPICS synApps support environments for IOC development.
BCDA-APSGenerate EPICS IOC database definitions with templates and macro-based substitutions.
mattbobambroseGenerate or update Markdown API documentation from build manifests and source trees.