trunk-post-migrate

Guides post-migration monitoring, cleanup, security hardening, and documentation after trunk-based migration merges.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill trunk-post-migrate-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trunk-post-migrate
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/dotnet/skills/trunk-post-migrate
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill trunk-post-migrate-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After merging a trunk-based development migration MR, teams face a scattered set of follow-up tasks—verifying pipelines, deleting stale branches, hardening security, and updating docs—that are easy to miss or execute inconsistently. ## Core Features & Use Cases - Deployment Monitoring: Checklists for the first main-branch pipeline and first production deployment, covering semantic release, NuGet publishing, K8s deployments, Auth0, and APIM verification. - Cleanup Automation: Deletes obsolete develop/staging branches, removes test migrations, and verifies old CI/CD files are gone. - Security & Quality Hardening: Tests read-only root filesystems, audits review app configurations, refactors flaky skipped tests, and suggests pipeline optimizations. - Use Case: After merging a .NET service's trunk migration MR, run this skill to walk through each post-migration phase interactively and produce a final status summary. ## Quick Start Run the trunk post-migration checklist against my trunk-migration-config.yaml to verify deployments and clean up old branches.

Frequently Asked Questions about trunk-post-migrate

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

FAQPage Schema
How do I verify a trunk-based migration after merging to main?

Run the post-migration checklist to monitor the first main pipeline, confirming semantic release versioning, git tags, NuGet package publishing, and dev/staging deployments across all regions. It then walks through production approval and health checks.

How to clean up develop and staging branches after trunk migration?

The skill asks for confirmation, then deletes the develop and staging branches both locally and remotely using git branch -d and git push origin --delete. It also verifies old .gitlab-ci and k8s directories are removed.

Does this work with GitLab CI/CD and Kubernetes deployments?

Yes, the checklists are built around GitLab CI pipelines, Kustomize-based Kubernetes deployments, GitLab Package Registry for NuGet, and Azure resources like ACR and APIM. It reads paths from trunk-migration-config.yaml.

What should I do if a post-migration deployment fails?

If any deployment fails during monitoring, the skill suggests running the trunk-troubleshoot skill with the error details. It does not attempt automatic rollback or remediation itself.

How do I fix flaky tests skipped during migration?

The skill searches for skipped tests via grep on Skip attributes, then recommends replacing fixed Task.Delay sleeps with a polling loop using a timeout and interval. It asks before refactoring any tests.