菜单
Ripple effect analysis patterns for COBOL change impact. Covers how changes propagate through CALLS, INCLUDES, and shared data relationships. Use when impact-analyzer agent is performing blast radius assessment.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | impact-analysis |
| description | Ripple effect analysis patterns for COBOL change impact. Covers how changes propagate through CALLS, INCLUDES, and shared data relationships. Use when impact-analyzer agent is performing blast radius assessment. |
Risk: LOW to MEDIUM Affects: Programs that directly CALL the changing program
MATCH (caller:Program)-[:CALLS]->(target:Program {program_id: $name})
RETURN caller.program_id, caller.estimated_complexity
Risk: MEDIUM to HIGH Affects: All programs in the call chain above the changed program
MATCH path = (upstream)-[:CALLS*1..]->(target:Program {program_id: $name})
RETURN upstream.program_id, length(path) AS depth
ORDER BY depth
Risk: HIGH (copybooks are shared) Affects: Every program that INCLUDEs the copybook, plus their callers
MATCH (p:Program)-[:INCLUDES]->(cb:Copybook {name: $name})
OPTIONAL MATCH (caller)-[:CALLS*1..5]->(p)
RETURN DISTINCT p.program_id AS direct, collect(DISTINCT caller.program_id) AS transitive
Risk: HIGH if item is widely used Strategy: Trace which paragraphs READ or WRITE files that use this data item
MATCH (cb:Copybook {name: $copybook})-[:DEFINES]->(di:DataItem {name: $item})
MATCH (p:Program)-[:INCLUDES]->(cb)
RETURN p.program_id, p.estimated_complexity
| Factor | Weight | Scoring |
|---|---|---|
| Direct caller count | 30% | 0 callers=0, 1-3=1, 4-7=2, 8+=3 |
| Transitive caller depth | 20% | depth 1=1, 2=2, 3+=3 |
| Copybook breadth | 25% | 1 program=0, 2-5=1, 6-10=2, 10+=3 |
| Program complexity | 15% | LOW=0, MEDIUM=1, HIGH=2, CRITICAL=3 |
| Risk flags | 10% | 0 flags=0, 1=1, 2=2, 3=3 |
Total score 0-3: LOW | 4-6: MEDIUM | 7-9: HIGH | 10-12: CRITICAL
Modernization analysis heuristics, complexity scoring rubrics, migration wave planning guidance, and interpretation of COBOL knowledge graph metrics. Use when graph-query, complexity-scorer, or migration-advisor needs to interpret results or make recommendations.
COBOL anti-patterns, modernization signals, and risk patterns to identify during parsing and analysis. Use when evaluating COBOL code quality, flagging migration risks, or assessing programs for Java conversion feasibility.
COBOL language grammar, division and section structure, PIC clause syntax, level numbers, procedure division verbs, and language construct reference. Use when parsing, analysing, or explaining COBOL source code structure.
Proven Cypher query and write patterns for the LegacyCobolInsights graph. Includes MERGE templates for ingestion, common traversal queries for analysis, and aggregation patterns for reporting. Use when writing to or querying Neo4j.
Mappings from COBOL constructs to Java equivalents. Covers data type mappings, control flow mappings, file I/O patterns, and Spring Boot architecture recommendations. Use when migration-advisor is producing Java blueprints for COBOL programs.
LegacyCobolInsights Neo4j knowledge graph schema. Node labels, properties, relationship types, and constraints for the COBOL modernization graph database. Use when reading from or writing to the Neo4j graph in this project.