Menu
Encodes technical requirements for rsyslog modules, including concurrency, metadata, and initialization.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
| name | rsyslog_module |
| description | Encodes technical requirements for rsyslog modules, including concurrency, metadata, and initialization. |
This skill captures the essential technical patterns for authoring and maintaining rsyslog modules (plugins/contrib).
assert() + if).pData (shared) vs WID (per-worker).BEGINmodInit, CODESTARTmodInit, etc.
Rsyslog v8 has a high-concurrency worker model.
pData): Mutable state shared across workers MUST be protected by a mutex in pData.WID): Never share wrkrInstanceData_t.assert(pData != NULL);
if (pData == NULL) {
// Handle error gracefully
}
Every module must implement and register standard entry points:
modInit(): Initialize static data and registry interfaces.modExit(): Finalize and cleanup.beginTransaction() / commitTransaction(): For efficient batch-based output.MODULE_METADATA.yaml in the module directory.doc/ai/module_map.yaml in sync with locking and concurrency changes.plugins/Makefile.am and configure.ac when adding new modules.tests/Makefile.am. See the rsyslog_test skill for details. This is critical for make distcheck validity.MODULE_TYPE(eMOD_OUT) and other macros from runtime/module-template.h.rsyslog_build: For compiling the module.rsyslog_test: For creating module-specific smoke tests.rsyslog_doc: For documentation requirements.Based on SOC occupation classification
Ensures compliance with rsyslog's strict commit message and branching policies.
Mirror rsyslog run_checks.yml container validation locally, including the change-gated Ubuntu 26.04 run-ci.sh check run, the clang static analyzer job, late prompt-based audit passes, Cubic review where applicable, service-skip validation, clean-tree rules, and container path caveats.
Standardizes testing and validation for rsyslog using the diag.sh framework.
Guidelines for maintaining structured, RAG-optimized documentation and module metadata.
Orchestrate long-running rsyslog issue-fix sessions with a rolling active set of work units, local issue cache use, separate worktrees, full validation gates, PR babysitting, merged-PR cleanup, and automatic refill until the selected issue class is exhausted.
Monitor rsyslog pull requests after push or rerun, including GitHub Actions checks, unresolved review threads, bot comments, reruns for known flakes, and concise status reporting.
