trunk-post-migrate

Guide post-migration monitoring, cleanup, security hardening, and documentation updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After trunk-based migrations, teams need a structured, repeatable checklist to ensure deployments are monitored, branches are cleaned up, security hardening is performed, and documentation is updated. This skill guides users through a phase-based workflow that reduces risk and accelerates release readiness.

Core Features & Use Cases

  • Monitor pipelines and deployments across main branch migrations to confirm successful rollout.
  • Cleanup old branches and migration artifacts to maintain a clean repository state.
  • Apply security hardening and update documentation and runbooks to reflect the new trunk-based workflow.

Quick Start

After merging the trunk-based migration MR to main, trigger this skill to guide you through monitoring, cleanup, security hardening, and documentation.

Frequently Asked Questions about trunk-post-migrate

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

FAQPage Schema
What is trunk-based migration post-deployment verification?▼

Trunk-based migration post-deployment verification confirms successful rollout by monitoring pipelines across Dev and Prod, cleaning up branches, applying security hardening, and updating documentation to ensure release readiness and reduce risk.

How do I automate branch cleanup after a trunk-based deployment?▼

Automate branch cleanup after a trunk-based deployment by triggering a phase-based workflow that removes old branches and migration artifacts, maintaining a clean repository state across main pipeline environments.

Does this trunk migration workflow support both Dev and Prod environments?▼

Yes, this trunk migration workflow applies to main pipeline and production deployment workflows across both Dev and Prod environments, covering branch cleanup, changelog updates, and verification checks.

How do I update documentation and runbooks after a trunk-based migration?▼

Update documentation and runbooks after a trunk-based migration by following a structured checklist that reflects the new workflow, ensuring security hardening and release readiness are properly documented.

When do I need a checklist for post-migration trunk deployment tasks?▼

You need a checklist for post-migration trunk deployment tasks after merging the migration MR to main, ensuring deployments are monitored, branches cleaned, security hardened, and documentation updated.