Verified:GitHub

trunk-migrate

Migrates .NET API services to trunk-based development with Kustomize manifests and GitLab CI/CD.

Updated Jul 22, 2026

Search Tags:#migration #kubernetes #dotnet #gitlab-ci #azure-functions #kustomize #trunk-based-development

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill trunk-migrate-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: trunk-migrate
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/dotnet/skills/trunk-migrate
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill trunk-migrate-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Migrating a .NET API service from GitLab Flow to trunk-based development requires manually rewriting Kubernetes manifests, restructuring CI/CD pipelines, and configuring review apps, which is error-prone and time-consuming. ## Core Features & Use Cases - Kustomize Manifest Generation: Creates base manifests, environment overlays, and region-specific kustomizations for webapi and Azure Functions services. - CI/CD Pipeline Rewrite: Generates a complete .gitlab-ci.yml with semantic release, review apps, production approval gates, and conditional jobs for Auth0, NuGet, EF migrations, and UI tests. - Security Hardening: Enforces non-root containers, non-privileged port 8080, and secretKeyRef-based secret management. - Use Case: A platform engineer needs to migrate a multi-service Azure Functions repo to trunk-based development; the skill reads the migration config, generates all Kustomize and CI files, validates builds, commits, and opens a GitLab MR. ## Quick Start Run /dotnet:trunk-migrate with the path to your trunk-migration-config.yaml after reviewing the plan from /dotnet:trunk-plan.

Frequently Asked Questions about trunk-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate a .NET service to trunk-based development?▼

Run /dotnet:trunk-discover and /dotnet:trunk-plan first, then execute /dotnet:trunk-migrate with your trunk-migration-config.yaml. The skill creates Kustomize manifests, rewrites .gitlab-ci.yml, validates builds, and opens a merge request.

How to set up Kustomize overlays for multiple environments?▼

The skill generates base manifests plus dev, staging, and prod overlays, then region-specific kustomizations for each region/environment combination. It validates every combination with kustomize build before committing.

Does trunk-migrate support Azure Functions services?▼

Yes, it supports functions-worker and functions-http service types, including multi-service repos. It generates KEDA ScaledObjects for workers, services and HPAs for HTTP functions, and uses $patch: replace overlays for secrets.

What prerequisites are required before running the migration?▼

You need a trunk-migration-config.yaml (from /dotnet:trunk-discover), the gitlab-ci plugin installed, and a reviewed migration plan. The skill stops and prompts if the gitlab-ci plugin is missing.

Why does the migration require user review before committing?▼

The skill modifies the repository destructively, deleting old K8s manifests and CI includes while rewriting .gitlab-ci.yml. It pauses with a full change summary and kustomize validation results so you can verify before commit and push.