sampler-build-debug

Diagnose Sampler-based PowerShell build and Pester 5 test failures.

11|1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/raandree/CopilotAtelier --skill sampler-build-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sampler-build-debug
Source: https://github.com/raandree/CopilotAtelier/tree/main/Skills/sampler-build-debug
Command: npx skills add https://github.com/raandree/CopilotAtelier --skill sampler-build-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging Sampler-based PowerShell module builds and Pester 5 test failures, with guidance to keep VS Code responsive. This skill helps teams diagnose build and test issues without freezing the editor and provides a safe workflow for diagnosing common mock/assertion failures and learning how to fix tests.

Core Features & Use Cases

  • Safe, detached build execution to prevent VS Code from freezing.
  • Read and interpret Pester results to diagnose mock and assertion failures.
  • Provide actionable steps to fix tests and rebuild modules.
  • Use Case: when a Sampler-based module build stalls or tests fail, apply this skill to reproduce, diagnose, and resolve the issue.

Quick Start

Run the detached build workflow described in this guide to reproduce failures and begin debugging.

Frequently Asked Questions about sampler-build-debug

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

FAQPage Schema
How do I debug failing Pester 5 tests without freezing VS Code?

Diagnose failing Sampler-based PowerShell module builds by running them in a detached pwsh process. This safe workflow prevents VS Code from freezing while you reproduce and investigate the build stalls.

Why does my Sampler PowerShell module build hang in VS Code?

Sampler builds hang because they block the VS Code editor thread. Execute builds in a detached pwsh process to keep the editor responsive while you safely reproduce and diagnose the underlying stall.

How do I diagnose Pester mock and assertion failures in a PowerShell module?

Diagnose Pester mock and assertion failures by reading and interpreting Pester 5 test results from a detached build run. This provides actionable steps to pinpoint common mock failures and fix the tests.

Can I run Sampler builds in a detached pwsh process to keep the editor responsive?

Yes, run Sampler builds in a detached pwsh process to keep VS Code responsive. This detached execution prevents the editor from freezing while you reproduce failures and debug tests.

What is the best way to fix failing Sampler-based PowerShell module builds?

The best way to fix failing Sampler-based PowerShell module builds is to reproduce failures in a detached pwsh process, read the Pester results, and apply actionable steps to fix tests and rebuild modules.