en un clic
ghcp-demo-ptbr
ghcp-demo-ptbr contient 4 skills collectées depuis RobertoBorges, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
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.
Business logic discovery, mapping, and preservation during application migration. **Use when:** Migrating any legacy application (any stack — .NET, Java, Python, Node.js, PHP, Ruby, Go, COBOL, Oracle Forms, etc.) 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.
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.
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.