migration-mapping
/migration-mapping
Create a mapping from source language files to target language files for code migrations. Use when evaluating or documenting a migration project.
- Author
- OpenHands ↗
- Repository
- extensions ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Create a mapping from source language files to target language files for code migrations. Use when evaluating or documenting a migration project.
Original author description
Create a mapping from source language files to target language files for code migrations. Use when evaluating or documenting a migration project.
How it works
- Task
- Output Format
- Rules
- How to Identify Mappings
- Example
- Verification
SKILL.md preview
---
name: migration-mapping
description: Create a mapping from source language files to target language files for code migrations. Use when evaluating or documenting a migration project.
license: MIT
compatibility: Requires completed migration with source and target code
triggers:
- migration mapping
- source target mapping
- file mapping
---
Create a mapping from source language files (e.g., COBOL) to target language files (e.g., Java) to document which target files implement the functionality of each source file.
## Task
Examine all source language files and identify the corresponding target language files that implement the same functionality. This mapping is essential for:
- Migration quality evaluation
- Traceability documentation
- Gap analysis
## Output Format
Save the mapping as a JSON file with this structure:
```json
{
"source_file_1.cbl": ["target_file_a.java", "target_file_b.java"],
"source_file_2.cbl": ["target_file_c.java"],
"source_file_3.cbl": []
}
```
## Rules
1. **Many-to-many mapping**: A source file may map to multiple target files, and a target file may implement logic from multiple source files
2. **Complete coverage**: EVERY source file must appear as a key in the mapping
3. **Complete target coverage**: EVERY target file should appear as a value at least once
4. **Empty arrays**: If a source file has no corresponding target implementation, use an empty array `[]`
5. **Incremental**: If a mapping file already exists, update it rather than replacing it
## How to Identify Mappings
Look for:
- Matching class/program names
- Similar function/paragraph names
- Matching business logic patterns
- Comments referencing source files
- Import/include statements
- Data structure similarities
## Example
For a COBOL-to-Java migration:
```json
{
"CALC001.cbl": ["InvoiceCalculator.java", "TaxCalculator.java"],
"CUST002.cbl": ["CustomerService.java", "CustomerRepository.java"],
"UTIL003.cbl": ["StringUtils.java"],
"SCREEN001.cbl": []
}
```
Note: `SCREEN001.cbl` maps to nothing because UI code was not migrated.
## Verification
After creating the mapping:
- [ ] Every source file is a key
- [ ] No duplicate keys
- [ ] Target files are relative paths from project root
- [ ] JSON is valid and well-formatted
Versions
The database has no other skills named migration-mapping.
Database snapshot: 13.11.2026 · package version 41bc091dd4de (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 84analyze-migrations
Analyze database migration files for safety issues before applying them to production. Use when the user says "check my migrations for safety issues", "review my database migrations", "are these migrations safe to run in production", "analyze my schema changes for locks or data… - 90component-migration-analysis
Create rendering-and-styling migration analysis docs for gen2 component migration. Use when on the "analyze rendering and styling" step for one or more components. - 100data-migration
Plans and scripts data migrations between SQL databases: schema mapping, type conversion, batched and resumable loading, validation and cutover. Use when the user mentions "data migration," "database migration," "migrate from MySQL to PostgreSQL," "schema migration," "ETL… - 100stream-feeds-migration
Generate the v2 -> v3 sync mapping for a Stream Activity Feeds app by sampling its live v2 activities and reactions and, when the app's v2 integration code is available, reading its write paths, and, from that code, plan how the app's code moves from v2 to v3. Use when setting… - 100mapping-data
Produces data mapping and data quality deliverables for interfaces, data flows and migrations - data dictionary, source-to-target mapping with transformation rules and code-value translations, data quality rules by dimension (completeness, validity, uniqueness, consistency,… - 96add-migration
Create and review a database migration for a finished model change (mapping configuration, generated model artifacts, permission chain, API contract) when the user explicitly invokes /add-migration.