gsd-undo

Revert GSD phase and plan commits while preserving dependency order.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-undo-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-undo
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-undo
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-undo-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk and guesswork from rolling back GSD work by helping you safely revert commits tied to phases or plans without accidentally breaking dependencies or losing context.

Core Features & Use Cases

  • Phase-aware rollback: Revert every commit associated with a specific phase using the phase manifest, with git log fallback when needed.
  • Plan-specific undo: Roll back only the commits for a single plan range when you need a narrower recovery path.
  • Interactive safety checks: Review recent GSD commits, validate dependencies, and confirm the target before execution.
  • Use Case: If a phase introduced a bad migration or a plan commit caused a broken build, this Skill helps you identify the exact rollback scope and execute it safely.

Quick Start

Use the gsd-undo skill to revert the target phase, plan, or recent commit set after confirming the rollback scope and safety checks.

Frequently Asked Questions about gsd-undo

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

FAQPage Schema
How do I revert git commits tied to a specific phase without breaking dependencies?

To revert git commits safely without breaking dependencies, you can roll back work associated with a specific phase using a phase manifest. The process requires commit discovery, dependency validation, and a confirmation gate before executing the rollback.

Can I undo a specific plan commit range instead of a full phase rollback?

Yes, you can execute a plan-specific undo to roll back only the commits for a single plan range. This provides a narrower recovery path when a specific plan commit causes a broken build, rather than reverting an entire phase.

What happens if the phase manifest is missing when I try to revert phase commits?

If the phase manifest is missing during a revert, the system uses a git log fallback to discover the relevant commits. This ensures you can still identify the target rollback scope even without direct manifest tracking.

Does this rollback process validate dependency order before executing the revert?

Yes, dependency validation is a core requirement before executing the revert. The system runs interactive safety checks to review recent commits, validate dependencies, and confirm the target scope to prevent breaking the repository state.

When should I use an interactive safety check for git history rollback?

You should use interactive safety checks whenever you need to revert git commits tied to phases or plans. This allows you to review recent commits, confirm the exact rollback scope, and prevent accidentally losing context or introducing bad migrations.

What is the best way to safely undo recent GSD commits in repositories using a phase manifest?

The best way to safely undo recent GSD commits is to use a process that applies commit discovery, manifest fallback, and dependency validation. This ensures you identify the exact rollback scope and confirm the target before executing any git history changes.