sampler-migration

Migrate legacy PowerShell module projects to the Sampler build framework.

11|1|Updated Mar 27, 2026

Search Tags:#automation #build #ci-cd #module #migrate #powershell #sampler

Ready to run

npx skills add https://github.com/raandree/CopilotAtelier --skill sampler-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sampler-migration
Source: https://github.com/raandree/CopilotAtelier/tree/main/Skills/sampler-migration
Command: npx skills add https://github.com/raandree/CopilotAtelier --skill sampler-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Step-by-step guide for migrating a legacy PowerShell module project to the Sampler build framework.

Core Features & Use Cases

Provides phased guidance for analyzing a legacy module, restructuring sources under source/, and configuring Sampler artifacts (build.ps1, GitVersion.yml, azure-pipelines.yml).
Demonstrates how to move from AppVeyor, PSDepend, PSDeploy, and Pester 4 to Sampler with ModuleBuilder, InvokeBuild, Pester 5, and GitVersion.
Includes best practices for setting up tests, packaging, changelog, and GitHub releases to support an end-to-end pipeline.

Quick Start

Start by inspecting the existing module, then initialize a Sampler-based project structure and run the bootstrap script to begin the migration.

Frequently Asked Questions about sampler-migration

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

FAQPage Schema

How do I migrate a legacy PowerShell module to the Sampler build framework?▼

To migrate a legacy PowerShell module to Sampler, inspect the existing project, restructure sources under the source/ directory, and configure build artifacts like build.ps1, GitVersion.yml, and azure-pipelines.yml. The process provides phased guidance for adapting your module to the Sampler build framework end-to-end.

What is the best way to move from AppVeyor and PSDepend to Sampler with ModuleBuilder?▼

Moving from AppVeyor, PSDepend, and PSDeploy to Sampler involves replacing them with ModuleBuilder, InvokeBuild, and GitVersion. This migration transitions your pipeline to Sampler's build framework, configuring build scripts and release pipelines for an end-to-end workflow.

How does upgrading from Pester 4 to Pester 5 work during a Sampler migration?▼

Upgrading from Pester 4 to Pester 5 during a Sampler migration involves configuring your test setup within the new Sampler-based project structure. The migration provides best practices for setting up tests using Pester 5 alongside ModuleBuilder and InvokeBuild in your build pipeline.

Can I use Sampler to set up a new PowerShell module project from scratch?▼

Yes, the Sampler migration process is adaptable to teams setting up new Sampler-based modules. You can initialize a Sampler-based project structure, run the bootstrap script, and configure build.ps1, GitVersion.yml, and azure-pipelines.yml to establish a complete CI/CD pipeline.

What source restructuring is needed when moving a PowerShell module to Sampler?▼

Source restructuring for Sampler requires moving your existing module files under the source/ directory. This reorganization aligns with Sampler's expected project layout, enabling proper packaging, automated testing, and release pipeline configuration.

Does Sampler support configuring GitHub releases and changelogs for PowerShell modules?▼

Yes, Sampler supports end-to-end pipeline configuration including GitHub releases and changelog generation. The migration guidance covers best practices for setting up packaging, changelog updates, and GitHub release automation within your azure-pipelines.yml workflow.