trunk-help

Explain trunk-based migration commands for .NET services from GitLab Flow.

Updated Aug 27, 2026

Search Tags:#workflow #guidance #migration #dotnet #gitlab-ci #kustomize #trunk-based

One-click install

npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill trunk-help

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: trunk-help
Source: https://github.com/onesmartguy/raptor-claude-plugins/tree/main/plugins/dotnet/skills/trunk-help
Command: npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill trunk-help

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explain trunk-based migration methodology and available commands for the dotnet trunk-based migration plugin.

Core Features & Use Cases

Overview of migrating from GitLab Flow to trunk-based development for .NET services.
Guidance on required artifacts (Kustomize manifests, shared pipeline templates, review apps) and gating.
Practical scenarios and decision points to apply the migration workflow.

Quick Start

Ask this skill for an overview of trunk-based migration to guide your .NET project migration plan.

Frequently Asked Questions about trunk-help

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

FAQPage Schema

What is trunk-based migration for .NET services?▼

The methodology transitions .NET services from GitLab Flow to trunk-based development. It guides developers through adopting Kustomize manifests, shared pipeline templates, and review apps for streamlined integration and deployment.

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

To migrate from GitLab Flow, follow the discover, plan, migrate, and validate workflows. This process establishes required artifacts like Kustomize manifests and shared pipelines to complete the .NET service transition.

When do I need Kustomize manifests and shared pipelines for .NET trunk-based migration?▼

You need Kustomize manifests, shared pipeline templates, and review apps when transitioning .NET services to trunk-based development. These artifacts establish gating and support the shared pipeline workflow.

What commands are available for the dotnet trunk-based migration plugin?▼

The plugin provides four workflows: dotnet:trunk-discover, dotnet:trunk-plan, dotnet:trunk-migrate, and dotnet:trunk-validate. These commands guide the complete migration lifecycle from planning to validation.

Can I use trunk-based migration for .NET projects without review apps?▼

Review apps are a required artifact for migrating .NET services to trunk-based development. The methodology mandates setting up review apps alongside Kustomize manifests and shared pipelines to ensure proper gating.