What problem does it solve? Trunk-based migrations of .NET services often fail with cryptic errors in Kustomize builds, GitLab CI pipelines, APIM configuration, or Auth0 setup, and engineers waste hours hunting down root causes that have been seen before. ## Core Features & Use Cases - Pattern-Based Diagnosis: Matches an error message or symptom against 13 known issue patterns covering Kustomize builds, health check ports, IngressRoute, APIM duplicates, review app variables, Auth0 secrets, NuGet jobs, production gates, flaky tests, matrix collisions, and connection strings. - Guided Fixes with Approval: Confirms the root cause by reading relevant files, explains the problem, proposes the fix, and asks for approval before changing anything. - Post-Fix Validation: Re-runs kustomize builds and YAML syntax checks after applying fixes, and falls back to general diagnostics for unknown issues. - Use Case: A pipeline fails with "readiness probe connection refused on port 80" after migration. Invoke the skill with the error text; it identifies the wrong health check port, applies the fix, and verifies the kustomize build passes. ## Quick Start Ask the assistant to troubleshoot a trunk migration issue by pasting the pipeline error message or describing the symptom you are seeing.
