القائمة
Guide framework and library migrations with incremental strategies, breaking change analysis, compatibility testing, and automated migration tools
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/wojons/skills --skill code-migrationيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Use when you need comprehensive accessibility auditing including WCAG compliance, legal requirements mapping, and user testing with disabilities
Apply systematic adversarial thinking patterns including devil's advocate, assumption busting, red teaming, and white hat security approaches
A 10-step methodology for building software with AI collaboration - from north star through automated Ralph loop execution with zero human-in-the-loop code writing
| name | code-migration |
| description | Guide framework and library migrations with incremental strategies, breaking change analysis, compatibility testing, and automated migration tools |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"developers, platform engineers, migration teams, architects","category":"maintenance"} |
Guide framework and library migrations with incremental strategies, breaking change analysis, compatibility testing, and automated migration tools to safely transition codebases between versions, frameworks, and architectures while minimizing risk and maintaining functionality.
Use this skill when:
def select_migration_strategy(project_characteristics):
"""
Select appropriate migration strategy based on project characteristics.
"""
strategies = {
'big_bang': {
'score': 0,
'conditions': ['small_codebase', 'low_complexity', 'minimal_dependencies']
},
'incremental': {
'score': 0,
'conditions': ['large_codebase', 'high_complexity', 'many_dependencies']
},
'parallel_run': {
'score': 0,
'conditions': ['business_critical', 'zero_downtime', 'high_availability']
},
'strangler_pattern': {
'score': 0,
'conditions': ['monolithic', 'legacy_system', 'gradual_replacement']
}
}
# Score each strategy based on project characteristics
for characteristic in project_characteristics:
for strategy_name, strategy_info in strategies.items():
if characteristic in strategy_info['conditions']:
strategy_info['score'] += 1
# Select highest scoring strategy
selected_strategy = max(strategies.items(), key= x: x[][])
{
: selected_strategy[],
: selected_strategy[][],
: generate_strategy_rationale(selected_strategy[], project_characteristics)
}
():
rationales = {
: ,
: ,
: ,
:
}
rationales.get(strategy, )
class BreakingChangeAnalyzer:
def __init__(self, source_api, target_api):
self.source_api = source_api
self.target_api = target_api
def analyze_breaking_changes(self):
"""Comprehensive breaking change analysis."""
analysis = {
'api_removals': self.find_removed_apis(),
'signature_changes': self.find_signature_changes(),
'behavior_changes': self.find_behavior_changes(),
'deprecations': self.find_deprecations(),
'new_requirements': self.find_new_requirements()
}
# Calculate migration complexity score
analysis['complexity_score'] = self.calculate_complexity_score(analysis)
analysis['migration_effort'] = self.estimate_migration_effort(analysis)
return analysis
def find_removed_apis(self):
"""Find APIs removed in target version."""
removed = []
for api in self.source_api:
if api not in self.target_api:
removed.append({
'api': api,
'type': ,
: ,
:
})
removed
():
changed = []
api .source_api:
api .target_api:
source_sig = .source_api[api][]
target_sig = .target_api[api][]
source_sig != target_sig:
changed.append({
: api,
: ,
: source_sig,
: target_sig,
: ,
:
})
changed
def create_incremental_migration_plan(codebase, migration_strategy):
"""
Create incremental migration plan with phases.
"""
phases = []
# Phase 1: Preparation
phases.append({
'phase': 1,
'name': 'Preparation & Setup',
'tasks': [
'Set up new framework/project structure',
'Configure build and deployment pipelines',
'Implement feature flags for migration control',
'Create compatibility layer/adapters',
'Set up monitoring and observability'
],
'success_criteria': [
'New project builds successfully',
'Feature flags operational',
'Monitoring configured',
'Rollback procedures tested'
]
})
# Phase 2: Dependency Migration
phases.append({
'phase': 2,
'name': 'Dependency Migration',
'tasks': [
'Migrate shared libraries and utilities',
'Update build dependencies',
'Create shared interfaces and contracts',
'Test library compatibility'
],
'success_criteria': [
'All dependencies compatible with both versions',
'Shared libraries functioning',
'Build system supports both versions'
]
})
# Phase 3: Component Migration
components = identify_migration_components(codebase)
for i, component_group (chunk_components(components, ), ):
phases.append({
: i,
: ,
: component_group,
: [
,
,
,
],
: [
,
,
,
]
})
phases.append({
: (phases) + ,
: ,
: [
,
,
,
,
],
: [
,
,
,
]
})
{
: (phases),
: calculate_duration(phases),
: phases,
: create_risk_mitigation_plan(phases)
}
# Analyze migration from Angular 12 to 16
npm run code-migration:analyze -- --source angular --source-version 12 --target angular --target-version 16 --codebase src/
# Create incremental migration plan
npm run code-migration:plan -- --strategy incremental --framework react --from 16 --to 18 --output migration-plan.json
# Generate automated migration scripts
npm run code-migration:generate -- --framework .net --from 4.8 --to 8.0 --codebase . --output migration-scripts/
# Test migration compatibility
npm run code-migration:test -- --source-code src/ --target-framework vue-3 --tests tests/ --output compatibility-report.json
# Execute phased migration
npm run code-migration:execute -- --plan migration-plan.json --phase 2 --dry-run
# Monitor migration progress
npm run code-migration:monitor -- --plan migration-plan.json --metrics coverage,performance,errors --dashboard
# Validate migration completeness
npm run code-migration:validate -- --source src/ --target dist/ --validation-tests tests/validation/
# Create rollback plan
npm run code-migration:rollback -- --plan migration-plan.json --trigger error-rate --threshold 1%
# Generate migration documentation
npm run code-migration:docs -- --plan migration-plan.json --template comprehensive --output docs/migration-guide.md
# Train team on migrated codebase
npm run code-migration:train -- --new-framework react-18 --training-modules all --output training-materials/
Code Migration Analysis Report
──────────────────────────────
Source: Angular 12 Application
Target: Angular 16
Analysis Date: 2026-02-26
Codebase Size: 45,328 lines, 247 files
Migration Strategy Recommendation: INCREMENTAL MIGRATION
Rationale: Large codebase with complex dependencies and business-critical functionality
Breaking Changes Analysis:
❌ Critical Changes: 12
⚠️ Medium Changes: 28
ℹ️ Minor Changes: 45
✅ Compatible: 320 APIs
Critical Breaking Changes:
1. ❌ Ivy Compiler Required (Impact: High)
• Current: View Engine compiler
• Required: Ivy compiler (Angular 13+)
• Migration: Update angular.json and tsconfig.json
• Effort: 8 hours
2. ❌ RxJS 7 Required (Impact: High)
• Current: RxJS 6.6.7
• Required: RxJS 7.8.0+
• Breaking Changes: Operator function changes, observable creation
• Effort: 16 hours
3. ❌ TypeScript 4.7+ Required (Impact: High)
• Current: TypeScript 4.2.4
• Required: TypeScript 4.7.2+
• Migration: Update tsconfig.json, fix type errors
• Effort: 12 hours
Dependency Analysis:
┌──────────────────────┬────────────┬────────────┬────────────┐
│ Dependency │ Current │ Required │ Status │
├──────────────────────┼────────────┼────────────┼────────────┤
│ @angular/core │ 12.2.16 │ 16.2.0 ❌ Upgrade │
│ @angular/cli │ 12.2.18 │ 16.2.0 ❌ Upgrade │
│ rxjs │ 6.6.7 │ 7.8.0 ❌ Upgrade │
│ typescript │ 4.2.4 │ 4.7.2 ❌ Upgrade │
│ zone.js │ 0.11.4 │ 0.13.0 ⚠️ Compatible │
│ @angular/material │ 12.2.13 │ 16.2.0 ❌ Upgrade │
└──────────────────────┴────────────┴────────────┴────────────┘
Code Impact Assessment:
• Components affected: 142 (57% of total)
• Services affected: 45 (92% of total)
• Directives affected: 18 (75% of total)
• Pipes affected: 12 (100% of total)
• Tests affected: 245 (98% of total)
Migration Complexity Score: 78/100 (High Complexity)
Estimated Effort: 120-160 hours (3-4 weeks)
Incremental Migration Plan:
Phase 1: Foundation (1 week)
• Update build system and dependencies
• Configure Ivy compiler
• Set up feature flags for migration
Phase 2: Core Libraries (1 week)
• Migrate RxJS to version 7
• Update TypeScript to 4.7+
• Update zone.js compatibility
Phase 3: Angular Core (2 weeks)
• Update @angular/core to v16
• Migrate @angular/cli
• Update component lifecycle methods
Phase 4: UI Libraries (1 week)
• Update @angular/material
• Migrate custom UI components
• Update CSS and theming
Phase 5: Testing & Validation (1 week)
• Update test utilities
• Run comprehensive tests
• Performance benchmarking
Risk Assessment:
• Technical Risk: HIGH (multiple breaking changes)
• Business Risk: MEDIUM (downtime during migration)
• Schedule Risk: MEDIUM (complex dependency chain)
• Team Risk: LOW (Angular expertise available)
Risk Mitigation Strategies:
1. Implement feature flags for gradual rollout
2. Maintain parallel branches during migration
3. Extensive automated testing
4. Regular stakeholder updates
5. Rollback procedures defined
Testing Strategy:
• Unit Tests: Update all 245 test files
• Integration Tests: Test component interactions
• E2E Tests: Verify user workflows
• Performance Tests: Compare before/after metrics
• Compatibility Tests: Verify browser support
Success Criteria:
1. All tests passing in new environment
2. Performance within 10% of baseline
3. Zero breaking changes in production
4. Team proficient with Angular 16 features
5. Documentation updated and complete
Tooling Recommendations:
1. Angular Update Guide (ng update)
2. RxJS upgrade helper
3. TypeScript migration scripts
4. Automated test migration tools
5. Performance monitoring setup
Next Steps:
1. Approve migration plan and timeline
2. Allocate development resources
3. Schedule migration window
4. Set up monitoring and alerting
5. Begin Phase 1 implementation
Migration Dashboard:
Status: PLANNING_COMPLETE
Current Phase: Preparation
Progress: 0%
Estimated Completion: 2026-03-26
Risks: 3 high, 2 medium, 1 low
{
"analysis": {
"source": "Angular 12 Application",
"target": "Angular 16",
"analysis_date": "2026-02-26",
"codebase_size": {
"lines": 45328,
"files": 247,
"components": 250,
"services": 49,
"directives": 24,
"pipes": 12
},
"recommended_strategy": "incremental",
"complexity_score": 78,
"estimated_effort_hours": 140
},
"breaking_changes"
Code Migration Dashboard
───────────────────────
Project: E-commerce Platform
Migration: Angular 12 → 16
Status: IN_PROGRESS
Current Phase: 3/5 (Angular Core Migration)
Progress Summary:
┌──────────────────────┬──────────┬────────────┬────────────┐
│ Phase │ Status │ Progress │ Timeline │
├──────────────────────┼──────────┼────────────┼────────────┤
│ 1. Foundation │ ✅ Done │ 100% │ Feb 19-26 │
│ 2. Core Libraries │ ✅ Done │ 100% │ Feb 26-Mar 5│
│ 3. Angular Core │ 🔄 Active│ 65% │ Mar 5-19 │
│ 4. UI Libraries │ ⏳ Pending│ 0% │ Mar 19-26 │
│ 5. Testing & Validation│ ⏳ Pending│ 0% │ Mar 26-Apr 2│
└──────────────────────┴──────────┴────────────┴────────────┘
Current Phase Details:
• Components migrated: 92/142 (65%)
• Services migrated: 28/45 (62%)
• Tests passing: 78% (191/245)
• Performance: Within 5% of baseline
• Issues: 12 open (3 critical, 5 medium, 4 low)
Recent Activity:
• Mar 12: Migrated checkout component (critical path)
• Mar 11: Fixed RxJS operator compatibility issue
• Mar 10: Updated authentication service
• Mar 9: Performance regression detected and fixed
Upcoming Tasks:
1. Migrate product catalog component (priority: high)
2. Update shopping cart service (priority: high)
3. Fix remaining TypeScript errors (priority: medium)
4. Update remaining unit tests (priority: medium)
Risks & Issues:
• ⚠️ Critical: Product image component migration delayed
• ⚠️ Medium: CSS theming inconsistencies
• ✅ Resolved: RxJS migration completed successfully
• ✅ Resolved: Build system configuration fixed
Metrics:
• Code Coverage: 78% (target: 85%)
• Performance: 95% of baseline (target: 90%+)
• Test Pass Rate: 92% (target: 95%+)
• Migration Velocity: 12 components/week
Next Milestone: Complete Phase 3 by Mar 19
Overall Progress: 42%
Estimated Completion: Apr 2, 2026