What problem does it solve? Working with the SharpPS.Shells PowerShell module requires knowing its pipeline conventions — folder-per-pipeline registration, numbered processor scripts, the shared $arguments hashtable, and the Update-Pipeline patch workflow — and mistakes can trigger real side effects like deployments, DB migrations, and software installs. ## Core Features & Use Cases - Pipeline execution guidance: Run shipped pipelines (artifact, install, publish, sif, sitecore, startup, traefik) via Start-Pipeline with the correct $arguments hashtable, predecessors, and -Help short-circuit behavior. - Runtime patching: Reshape an already-registered pipeline with Update-Pipeline using Replace, InsertBefore, InsertAfter, MoveTo, or Remove without editing shipped .ps1 files. - Module setup: Register the SharpPSGallery MyGet repository and install the module idempotently, choosing the right PowerShell host (pwsh vs powershell) per platform. - Use Case: You need a Slack notification step after the publish step of the sitecore pipeline. Get the processor with Get-Pipeline, then call Update-Pipeline -Processor $publishStep -Path "C:\custom\01b-NotifySlack.ps1" -Action InsertAfter to splice it in for the session. ## Quick Start Ask the assistant to run the SharpPS sitecore pipeline with a custom PublishUrl argument using pwsh, after confirming the plan and arguments.
