What problem does it solve? Migrating .NET services to trunk-based development requires gathering dozens of configuration values scattered across solution files, Dockerfiles, Kubernetes manifests, and GitLab CI pipelines. This Skill automates that discovery by scanning the repository, extracting existing settings, and producing a complete trunk-migration-config.yaml file. ## Core Features & Use Cases - Automated Repository Scanning: Detects solution files, projects, Dockerfiles, service types (webapi, functions-http, functions-worker), K8s manifests, KEDA triggers, and CI/CD variables. - Interactive Gap-Fill: Prompts for values that cannot be auto-detected, such as ACR registries, AKS clusters, Key Vault names, APIM API IDs, and Jira ticket IDs. - Config Generation: Writes a validated trunk-migration-config.yaml supporting single-service and multi-service repos, including Azure Functions and multi-region setups. - Use Case: A platform engineer migrating a .NET API service to trunk-based development runs discovery to auto-extract namespaces, New Relic app names, health check paths, and gateway settings instead of manually auditing every manifest. ## Quick Start Ask the assistant to scan this .NET repository and generate the trunk migration configuration file.
