plc-code-analysis

# plc-code-analysis ## Goal Perform structured, multi-perspective security and quality analysis of PLC code, producing a severity-ranked findings report. Acts as an automated "second pair of eyes" for automation engineers. ## Independence from tia-openness-roadmap This skill is NOT routed by `tia-openness-roadmap`. It has its own trigger patterns and operates independently. The Openness roadmap handles engineering automation (create, modify, import/export via API). This skill handles analysis and review of existing code. The skill can consume code retrieved through an integration or exported through Openness/VCI, but it does not depend on a particular wrapper. ## Input recognition PLC code commonly arrives in one of four ways. Identify the exact format and provenance before analysis. ### Format 1 — Raw SCL / Structured Text The user pastes or uploads `.scl`, `.st`, or plain-text PLC code. This is the simplest case. Parse directly as text. Look for FUNCTION_BLOCK, FUNCTION, ORGANIZATION_BLOCK, DATA_BLOCK headers to identify block boundaries. ### Format 2 — SIMATIC SD source documents (V21) TIA Portal V21 can export S7-1200/S7-1500 SCL, LAD, FBD, DB, F-DB, UDT, and F-UDT content in the text-based SIMATIC Source Document format. Analyze the `.s7dcl` declaration/code document together with its `.s7res` resources when both exist. Preserve document paths and identifiers so findings can be traced back. SIMATIC SD is a source representation, not runtime evidence. In parti...