원클릭으로
GHCP-PromptMigration
GHCP-PromptMigration에는 RobertoBorges에서 수집한 skills 12개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.
이 저장소의 skills
Generate an executive-ready Migration Strategy Report (HTML deck) from a customer portfolio — CMDB exports, RVTools/Azure Migrate inventories, DMA outputs, vendor proposals, architecture diagrams. **Use when:** producing a CIO-ready migration plan for a customer portfolio (apps, databases, infra, or any mix). Starts the Portfolio Planning flow for multi-app engagements. **Triggers:** "generate migration report", "analyze CMDB", "portfolio analysis", "migration strategy report for X", "RVTools export analysis", "Azure Migrate analysis", "portfolio assessment", "build a deck from these artifacts". **Covers:** auto-detected workload pillars (Apps/DB/Infra), CAF-aligned 6 Rs classification, deterministic Factory / ISD-Partner / Unknown ownership, phased roadmap, dependency mapping, move groups, risks, executive HTML output.
Shifts model selection to cost-optimized alternatives when economy mode is active
Determines which LLM model to use for each agent spawn
Find and resume interrupted Copilot CLI sessions using session_store queries
Docker containerization patterns for .NET and Java applications targeting Azure. **Use when:** Creating Dockerfiles or deploying to Container Apps, App Service containers, or AKS. **Triggers on:** Container Apps or AKS selected as hosting platform, Docker-related requests. **Covers:** Multi-stage Dockerfiles, docker-compose, Container Apps configuration, health checks, resource limits.
Azure Infrastructure as Code patterns using Bicep and Terraform. **Use when:** Generating IaC for App Service, Container Apps, or AKS deployments. **Triggers on:** Phase 3 infrastructure generation, azd init, Bicep/Terraform file creation. **Covers:** Azure Verified Modules, managed identities, Key Vault with RBAC, Application Insights, networking.
Business logic discovery, mapping, and preservation during application migration. **Use when:** Migrating .NET or Java applications and need to ensure all business logic is preserved. **Triggers on:** Phase 2 code migration, business rule identification, logic preservation verification. **Covers:** Business rule extraction, logic mapping between source/target, validation tracking, media asset preservation. **Critical:** Ensures no business logic is lost during migration by creating traceable mappings.
Configuration file transformation patterns for .NET and Java modernization. **Use when:** Converting legacy config files to modern cloud-native formats. **Triggers on:** web.config, app.config, applicationContext.xml, persistence.xml files. **Covers:** web.config to appsettings.json, XML to YAML/properties, connection string externalization.
.NET Framework to .NET 10+ modernization patterns. **Use when:** User has a .NET Framework 4.x application and needs to upgrade to .NET 10 LTS. **Triggers on:** .csproj files with TargetFrameworkVersion, web.config files, System.Web references, Entity Framework 6. **Covers:** Project file transformation, web.config to appsettings.json, EF6 to EF Core, Windows/Forms auth to Entra ID.
Java EE and legacy Java to modern Spring Boot migration patterns. **Use when:** User has a Java EE, J2EE, or legacy Java 8/11 application and needs to upgrade to Spring Boot 3.x with Java 21. **Triggers on:** pom.xml with javax.* dependencies, web.xml files, EJB annotations, JAAS configuration. **Covers:** EJB to Spring beans, XML to Java/YAML config, JAAS to Spring Security OAuth2, JPA/Hibernate updates.
Unit testing patterns for validating migrated applications. **Use when:** Creating tests to verify migration correctness and prevent regressions. **Triggers on:** Test creation requests, validation phase, post-migration verification. **Covers:** xUnit/NUnit for .NET, JUnit 5 for Java, mocking strategies, test organization patterns.
WCF to REST API migration patterns for .NET modernization. **Use when:** Converting WCF services to ASP.NET Core REST APIs. **Triggers on:** .svc files, ServiceContract attributes, OperationContract, DataContract, WCF bindings. **Covers:** ServiceContract to controllers, DataContract to DTOs, FaultContract to Problem Details, OpenAPI generation. **Important:** This is a rewrite, not a compatibility layer. Existing WCF clients will need updates.