trunk-migrate

Automate trunk-based migration for .NET API services with Kustomize manifests and CI/CD updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill trunk-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trunk-migrate
Source: https://github.com/onesmartguy/raptor-claude-plugins/tree/main/plugins/dotnet/skills/trunk-migrate
Command: npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill trunk-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end trunk-based migration for a .NET API service, including generating Kustomize manifests, establishing environment overlays, region-specific patches, and updating CI/CD pipelines.

Core Features & Use Cases

  • Create Kustomize base manifests and overlays for dev, staging, and prod across multiple regions
  • Establish region-aware image replacements, New Relic patching, and review-app overlays for safe MR reviews
  • Drive the migration process with a structured plan, validation, and optional EF migrations

Quick Start

Start by reviewing the migration plan with /dotnet:trunk-plan, then execute the migration with /dotnet:trunk-migrate.

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 API service to trunk-based development with Kustomize and GitLab CI/CD?

Trunk-based migration for a .NET API service is automated by generating Kustomize base manifests, establishing environment overlays for dev, staging, and prod, and updating GitLab CI/CD pipelines with region-specific patches and image replacements.

What is the best way to structure Kustomize overlays for multi-region .NET deployments?

Structuring Kustomize overlays for multi-region .NET deployments requires creating base manifests, environment-specific overlays, and region-specific kustomizations with regional image replacements and New Relic patching to manage configurations across dev, staging, and prod.

Can I include Entity Framework migrations when automating a .NET trunk-based migration?

Entity Framework migrations are supported as an optional step during the .NET trunk-based migration process, allowing you to apply database schema updates alongside generating Kustomize manifests and updating CI/CD pipelines.

Does this trunk-based migration approach support review-app overlays for GitLab merge requests?

Review-app overlays for safe merge request reviews are supported by the trunk-based migration process, enabling isolated environment validation within GitLab CI/CD before merging changes to the main .NET service branches.

How do I validate a .NET trunk-based migration after generating Kustomize manifests and CI/CD pipelines?

Validating a .NET trunk-based migration involves running structured validation steps built into the migration process to ensure Kustomize manifests, environment overlays, and GitLab CI/CD pipelines are correctly configured before deployment.