session-undo

Manage Roslyn MCP workspace change history with revert and reload workflows.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill session-undo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-undo
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/skills/session-undo
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill session-undo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables you to view and manage the per-session history of changes made by Roslyn MCP, enabling reliable undo and workspace recovery without touching git.

Core Features & Use Cases

  • Session-scoped history: track tool-driven mutations for a workspace.
  • Revert latest apply: undo only the most recent solution-level change for a session.
  • Workspace reload: re-read from disk when external edits occur or snapshots are stale.
  • Atomic apply with verify: wrap apply, compile_check, and revert in a single safe operation to roll back on errors.
  • Use Case: a bad refactoring leaves the workspace in a broken state; you can review changes and revert to the pre-apply snapshot.

Quick Start

Determine the current session and run the undo workflow to review changes and, if needed, revert the last apply.

Frequently Asked Questions about session-undo

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

FAQPage Schema
How do I revert workspace changes made by Roslyn MCP without using git?▼

To revert workspace changes without using git, you can use the session history feature to undo only the most recent solution-level apply made during your Roslyn MCP session. This restores the workspace to its pre-apply snapshot safely.

What is the best way to review applied mutations in a Roslyn MCP session?▼

The best way to review applied mutations is to list the per-session history of tool-driven changes. This tracking mechanism records workspace mutations, allowing you to inspect recent applies before deciding whether to keep or revert them.

Can I reload my workspace from disk after external edits occur in Roslyn MCP?▼

Yes, you can reload your workspace from disk to re-read files when external edits occur or snapshots become stale. This ensures your active session synchronizes with the actual file state on disk.

Does Roslyn MCP support atomic apply with verify and automatic rollback?▼

Yes, Roslyn MCP supports atomic apply with verify by wrapping apply, compile_check, and revert in a single safe operation. If the compile check fails, the workflow automatically rolls back to the previous state.

Why should I use session-scoped history instead of git to undo a bad refactoring?▼

Session-scoped history targets tool-driven mutations within your active workspace, letting you quickly revert a bad refactoring without affecting your git history. It provides a lightweight recovery mechanism for broken solution states.

Are there limitations to reverting changes in a Roslyn MCP workspace?▼

The main limitation is that reversion only targets the most recent apply within the current session. You cannot undo multiple older mutations sequentially, and you must reload the workspace if external disk drift occurs.