rpg-migration-analyzer
Analyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Ja
npx skills add majiayu000/claude-skill-registry --skill rpg-migration-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# RPG Migration Analyzer Analyzes legacy RPG programs (RPG III/IV/ILE) from AS/400 and IBM i systems for migration to modern Java applications, extracting business logic, data structures, file operations, and generating actionable migration strategies. ## Overview This skill provides comprehensive analysis and migration planning for RPG (Report Program Generator) applications. It extracts program specifications, converts RPG data types to Java equivalents, maps file operations to modern database access patterns, and generates implementation-ready Java code structures. **Key Migration Focus**: RPG to Java with proper handling of packed decimals (BigDecimal), data structures (POJOs), file operations (JPA/JDBC), indicators (boolean variables), and business logic preservation. ## When to Use This Skill Use this skill when: - Analyzing RPG source files (.rpg, .rpgle, .RPGLE) for modernization - Planning migration from AS/400 or IBM i systems to Java - Converting RPG data structures (D-specs) to Java classes - Mapping RPG file operations (F-specs) to database access patterns - Understanding RPG program dependencies and call chains - Generating Java code equivalents from RPG business logi
- Overview
- When to Use This Skill
- Core Capabilities
- 1. Program Analysis
- 2. Data Structure Mapping
- 3. File Operations
- 4. Java Migration Strategy
- 5. Dependency Analysis
- Instructions
- Step 1: Locate RPG Source Files
- Step 2: Analyze Program Structure
- Step 3: Map Data Types
- Step 4: Convert Code Patterns
- Step 5: Generate Java Implementation
find . -name "*.rpg" -o -name "*.rpgle" -o -name "*.RPGLE" python scripts/extract-structure.py PROGRAM.rpgle --output structure.json python scripts/generate-java-classes.py structure.json --output-dir ./src/main/java python scripts/estimate-complexity.py structure.json --report complexity-report.md
What does the rpg-migration-analyzer skill do?
Analyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Ja
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill rpg-migration-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
