shakedown-workflow

Automates behavioral verification of the PPDS workflow using throwaway worktrees and generates a consolidated report.

5|1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill shakedown-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shakedown-workflow
Source: https://github.com/joshsmithxrm/power-platform-developer-suite/tree/main/.claude/skills/shakedown-workflow
Command: npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill shakedown-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Behavioral integration testing of the entire PPDS workflow, creating disposable worktrees, running pipelines with PPDS_SHAKEDOWN=1, collecting results, executing retro analysis, producing a report, and cleaning up.

Core Features & Use Cases

  • Create throwaway worktrees from the current branch for isolated testing.
  • Run pipelines with PPDS_SHAKEDOWN=1 to ensure deterministic runs and avoid real PR or issue actions.
  • Collect results, run retro, and generate a consolidated report to verify workflow integrity.

Quick Start

Execute the shakedown workflow to validate the end-to-end PPDS pipeline in a disposable, read-only test environment.

Frequently Asked Questions about shakedown-workflow

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

FAQPage Schema
How do I automate end-to-end behavioral testing for development pipelines without triggering real pull requests?

End-to-end behavioral testing for development pipelines can be automated by creating throwaway worktrees and executing pipelines with PPDS_SHAKEDOWN=1. This ensures deterministic runs and prevents real pull request or issue actions during validation.

What is a shakedown test for PPDS workflows and when should I use it?

A shakedown test for PPDS workflows is an automated behavioral verification of the entire development pipeline using isolated worktrees. Use it for pre-release validation across feature and bug scenarios to safely catch regressions and verify retro and reporting steps.

How do I run pipeline tests in isolated environments to catch workflow regressions?

You can run pipeline tests in isolated environments by creating disposable worktrees from your current branch. The shakedown workflow executes pipelines within these isolated worktrees to safely verify workflow integrity and catch regressions before release.

Can I execute read-only pipeline testing without modifying my main repository branch?

Yes, you can execute read-only pipeline testing by creating throwaway worktrees from your current branch. This approach satisfies requirements for safe read-only operation and deterministic test execution without modifying your main repository branch.

How are pipeline test results collected and aggregated after a workflow shakedown?

Pipeline test results are collected and aggregated through a structured artifact collection process after the workflow shakedown. The automated workflow executes retro analysis on the results and produces a consolidated report to verify overall workflow integrity.

What are the limitations of using throwaway worktrees for pre-release validation?

Using throwaway worktrees for pre-release validation limits testing to read-only operations and deterministic runs controlled by PPDS_SHAKEDOWN=1. It focuses on behavioral verification of existing pipelines rather than generating new test scenarios or modifying real issues.