gsd-undo

Revert GSD-managed phases and plans with dependency validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the risk of breaking project state when rolling back changes in complex GSD workflows by providing a structured, dependency-aware revert mechanism.

Core Features & Use Cases

  • Phase-based Reversion: Roll back entire project phases using manifest tracking to ensure all associated commits are identified.
  • Dependency Checks: Automatically validates that reverting a commit won't break downstream dependencies or plan integrity.
  • Interactive Selection: Use the last N commits mode to safely browse and select specific GSD-managed changes for rollback.

Quick Start

Invoke the gsd-undo skill with the --last 5 flag to interactively select and revert from your five most recent GSD commits.

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 in a complex workflow without breaking dependencies?

Dependency-aware git revert validates downstream plan integrity against phase manifests before executing rollback, ensuring non-destructive state restoration that preserves repository stability across complex workflows.

Can I roll back an entire project phase using git history analysis?

Phase-based reversion uses manifest tracking against git history to identify and roll back all commits associated with an entire project phase, executing granular state restoration for complex workflows.

How do I interactively select specific commits to revert from recent git history?

Interactive selection mode browses recent git history using the last N commits flag, allowing targeted selection and rollback of specific GSD-managed changes without affecting unrelated repository state.

Does this git revert workflow require integration with core project management logic?

Granular rollback of phases requires integration with core workflow logic and phase manifests, validating dependencies against project plans to maintain repository integrity during non-destructive state restoration.

What happens if reverting a git commit breaks downstream dependencies in my project?

Automated dependency checks validate downstream plan integrity before executing rollback, preventing reverts that would break dependencies and ensuring non-destructive state restoration across the repository history.