workflow-stage-editor-quality-gate

Validate workflow-editor stage features with build, unit, Storybook, and Playwright tests.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-stage-editor-quality-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-stage-editor-quality-gate
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.claude/skills/workflow-stage-editor-quality-gate
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill workflow-stage-editor-quality-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of validating multi-layered workflow editor changes, ensuring that modifications to stage creation, editing, and deletion do not break the interconnected UI and API components.

Core Features & Use Cases

  • Comprehensive Validation: Orchestrates a multi-stage audit covering build integrity, unit tests, Storybook rendering, and end-to-end Playwright scenarios.
  • Regression Protection: Specifically guards against regressions in graph/list workspace behavior, inspector editing, and action-catalog discovery.
  • Use Case: When a developer implements a new stage-editing feature, this Skill provides the exact sequence of tests to verify that the UI, API, and keyboard accessibility remain fully functional.

Quick Start

Execute the workflow-stage-editor-quality-gate skill to run the full suite of build, unit, and end-to-end tests against your current workflow-editor changes.

Frequently Asked Questions about workflow-stage-editor-quality-gate

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

FAQPage Schema
How do I validate Umbraco workflow editor changes across UI and API layers?

Validate Umbraco workflow editor changes by running a multi-stage audit that executes build, unit, Storybook, and Playwright test suites to ensure contract and functional consistency across both client-side and server-side components.

What is the best way to prevent regressions when editing workflow stages in Umbraco?

To prevent regressions when editing workflow stages, execute a comprehensive test suite that guards graph/list workspace behavior, inspector editing, and action-catalog discovery against breaking changes introduced during stage creation or deletion.

Do I need Playwright and Storybook to test workflow stage creation and editing?

Yes, executing both Storybook rendering and end-to-end Playwright scenarios is required alongside build and unit tests to fully verify the UI, API, and keyboard accessibility remain functional during workflow stage creation and editing.

How does a workflow editor quality gate handle complex UI state management?

A workflow editor quality gate handles complex UI state management by orchestrating a multi-stage audit that validates modifications to stage creation, editing, and deletion do not break interconnected client-side and server-side components.

Can I run a single test to check workflow editor integrity?

No, checking workflow editor integrity requires executing the full suite of build, unit test, Storybook rendering, and end-to-end Playwright tests to ensure complete contract and functional consistency across all layers.

Why does my workflow editor break after modifying stage creation features?

Your workflow editor may break after modifying stage creation features because interconnected UI and API components require comprehensive validation through build, unit, Storybook, and Playwright test suites to prevent regressions.