ue-editor-automation-workflow

Automate Unreal Editor and UnrealEditor-Cmd runs with Pester test orchestration.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/moraluco/Illusion-Cursor-dev-kit --skill ue-editor-automation-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ue-editor-automation-workflow
Source: https://github.com/moraluco/Illusion-Cursor-dev-kit/tree/main/.cursor/skills/ue-editor-automation-workflow
Command: npx skills add https://github.com/moraluco/Illusion-Cursor-dev-kit --skill ue-editor-automation-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reliable, auditable workflow for running automation that requires the Unreal Editor, reducing flakiness, preventing lost work, and producing reproducible evidence for tests and investigations.

Core Features & Use Cases

  • Mode selection: Choose between interactive Editor+Bridge for asset and blueprint queries or unattended UnrealEditor-Cmd for CI/nightly runs.
  • Safety & persistence: Enforces immediate saves, milestone checkpoints, and rollback-on-failure practices to avoid half-broken assets.
  • Resource governance & observability: Controls concurrency, enforces memory/instance guards, isolates outputs per run, and captures logs/screenshots for postmortem.
  • Testing integration: Orchestrates Pester unit and optional E2E runs, plus guidance for C++ builds, Live Coding caveats, and restart needs.

Quick Start

Start the UE Editor automation workflow to launch or reuse an Editor instance, wait for bridge connectivity if needed, run tests or queries, collect logs and screenshots, and apply save/rollback policies for safe, reproducible results.

Frequently Asked Questions about ue-editor-automation-workflow

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

FAQPage Schema
How do I automate Unreal Editor for CI testing without losing assets to crashes?

Unreal Editor automation reduces flakiness by enforcing immediate saves, milestone checkpoints, and rollback-on-failure policies during runs. This prevents half-broken assets and ensures reproducible test artifacts.

What is the difference between interactive Editor and UnrealEditor-Cmd for automation?

Interactive Editor with bridge connectivity supports blueprint and asset queries, while unattended UnrealEditor-Cmd handles CI or nightly runs. Both modes capture logs and screenshots for postmortem analysis.

How do I run Pester tests with Unreal Engine automation workflows?

You can orchestrate Pester unit and optional E2E test runs alongside your Unreal Editor automation. The workflow manages startup, resource gating, and evidence collection for the Pester test execution.

Does this Unreal Editor automation workflow support concurrency and memory guards?

Yes, the workflow controls concurrency, enforces memory and instance guards, and isolates outputs per run. This resource governance prevents system overload during unattended UnrealEditor-Cmd scenarios.

Why does Live Coding require restarts during C++ automation builds in Unreal?

The workflow provides specific C++ build guidance and highlights Live Coding caveats that necessitate editor restarts. Following this guidance ensures stable C++ builds during your automation runs.

How do I collect screenshots and logs from Play In Editor automation runs?

The workflow captures logs and screenshots from PIE and other automation runs, isolating outputs per run for postmortem analysis. This produces reproducible test artifacts for your investigations.