gsd-undo

Revert GSD phase or plan commits with dependency validation and confirmation gating.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-undo-electroheadfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-undo
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-undo
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-undo-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you safely revert GSD phase or plan commits without blindly undoing unrelated work, reducing the risk of breaking dependencies or losing important progress.

Core Features & Use Cases

  • Phase rollback: Revert every commit associated with a specific GSD phase using the phase manifest and git history fallback.
  • Plan rollback: Undo a targeted plan range when you need to back out a focused set of changes.
  • Safety checks: Verifies dependencies and requires a confirmation gate before execution so reversions happen intentionally.
  • Use case: A developer notices a recent planning phase introduced regressions and uses the Skill to identify the correct commits, validate impact, and revert only the affected work.

Quick Start

Use the gsd-undo skill to safely revert phase 12 while checking dependencies and asking for confirmation before any changes.

Frequently Asked Questions about gsd-undo

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

FAQPage Schema
How do I safely revert git commits for a specific development phase without breaking dependencies?

Plan rollback targets a focused commit range to undo a specific set of changes, whereas phase rollback reverts every commit associated with a specific development phase using the phase manifest and git history fallback.

How do I undo a git commit range while checking for dependency conflicts?

Dependency checks verify that reverting a specific commit will not break downstream requirements before execution. This validation ensures reversions happen intentionally by validating impact against the phase manifest and git history.

What is the best way to roll back structured workflow changes tracked by phase manifests?

The best way to roll back structured workflow changes is to perform a manifest lookup to identify the correct commits, validate dependencies, and apply controlled git revert operations. This ensures you only revert the affected work without losing important progress.

Can I revert multiple git commits associated with a single development phase at once?

Yes, you can revert multiple git commits associated with a single phase by using the phase manifest to group the related commits. The rollback process identifies the full commit range for that phase and executes a controlled git revert sequence.