unity-workflow

Name: unity-workflow
Availability: InStock
Author: yiduandtdt

Track operation history, snapshots, and undo/redo across Unity editor sessions.

1|Updated May 21, 2026

Search Tags:#automation #workflow #unity #history #session #undo #snapshot

Ready to run

npx skills add https://github.com/YiDuandtdt/Bone-Throne --skill unity-workflow-yiduandtdt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unity-workflow
Source: https://github.com/YiDuandtdt/Bone-Throne/tree/main/.agents/skills/unity-skills/skills/workflow
Command: npx skills add https://github.com/YiDuandtdt/Bone-Throne --skill unity-workflow-yiduandtdt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides persistent operation history, snapshots, and undo/redo capabilities across tasks, sessions, and conversations to stabilize AI-driven work.

Core Features & Use Cases

Persistent history and time-travel style undo/redo for Unity editor workflows.
Snapshot and bookmark management to capture state before modifications and quickly navigate to important scenes or assets.
Planning, batching, and retry support for complex task sequences and validation in batch operations.

Quick Start

Open a Unity project, start a workflow session, perform actions, then end the session to save the history.

Frequently Asked Questions about unity-workflow

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

FAQPage Schema

How do I track Unity editor changes and undo modifications across different sessions?▼

To track Unity editor changes and undo modifications across sessions, use a persistent operation history system that records snapshots and supports undo/redo across tasks and conversations. This requires starting a workflow session, performing actions, and ending the session to save the history.

What is the best way to capture Unity scene snapshots before applying AI-driven modifications?▼

The best way to capture Unity scene snapshots before applying AI-driven modifications is using a snapshot management system that requires explicit session and task boundaries. This captures state before modifications, allowing quick navigation to important scenes or assets and safe undoing of changes.

Can I batch retry Unity asset validation and generate plans for complex task sequences?▼

Yes, you can batch retry Unity asset validation and generate plans for complex task sequences using planning, batching, and retry support. This functionality is designed for complex task sequences and validation in batch operations within a defined workflow session.

Does Unity workflow automation support time-travel style undo and redo for assets?▼

Yes, Unity workflow automation supports time-travel style undo and redo for assets by providing persistent history and safe undo/redo APIs. This ensures recoverability and stabilizes AI-driven work by reverting to previous states captured before modifications.

Why do I need explicit session boundaries to record Unity operation history?▼

You need explicit session boundaries to record Unity operation history because the system requires defined start and end points to safely persist snapshots and undo/redo states. This structure ensures changes are recoverable and prevents history from bleeding across unrelated tasks.

What are the limitations of using snapshots for Unity editor workflows?▼

The main limitation of using snapshots for Unity editor workflows is the strict requirement for explicit session and task boundaries. You must capture snapshots before making modifications and rely on safe undo/redo APIs, meaning un-snapshotted changes may not be recoverable.