undo-dev

Integrate Undoable commands and history management into frename workflows.

1|Updated Jan 23, 2026

Search Tags:#rust #history #undo #redo #software-architecture #command-pattern #frename

Ready to run

npx skills add https://github.com/Zelenov/frename --skill undo-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: undo-dev
Source: https://github.com/Zelenov/frename/tree/main/.claude/skills/undo-dev
Command: npx skills add https://github.com/Zelenov/frename --skill undo-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps engineers implement a robust undo/redo workflow for frename by detailing how to integrate Undoable commands with History, UndoContext, and UI wiring to enable safe state restoration.

Core Features & Use Cases

Provides the Undoable trait, the History container for undo/redo stacks, and the UndoContext for operation context.
Demonstrates how to integrate core undo mechanics with FolderWorkspace, including wiring NavigateFileCommand and ReorderTagCommand.
Supports debugging, extension, and safe error handling for end-to-end undo/redo workflows.

Quick Start

Wire Undo/Redo messages to the History and UndoContext in FolderWorkspace to begin implementing end-to-end undo support.

Frequently Asked Questions about undo-dev

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

FAQPage Schema

How do I implement undo and redo functionality in Rust applications?▼

To implement undo and redo in Rust, you define an Undoable trait and manage History stacks to enable safe state restoration and deterministic replay of operations.

What is the best way to wire undo and redo commands to a workspace UI in Rust?▼

The best way to wire undo and redo commands is by routing Undo and Redo messages through an UndoContext within your FolderWorkspace, connecting UI triggers directly to the History stacks.

How does the command pattern handle state restoration for undoable file operations?▼

The command pattern handles state restoration by wrapping file operations like NavigateFileCommand in an Undoable interface that captures UndoContext, enabling deterministic replay and safe state restore.

Can I extend existing undoable operations to support custom reordering logic?▼

Yes, you can extend undoable operations by implementing the Undoable trait for custom commands like ReorderTagCommand, integrating them with the History container for proper undo and redo stack management.

How do you handle errors during state restoration when executing undo workflows?▼

Error handling during state restoration is managed through the UndoContext, ensuring that operations failing during undo or deterministic replay are safely caught without corrupting the History stacks.