gsd-undo

Revert git changes by phase or plan with dependency validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reverting git changes can be risky when they belong to a phase or plan with dependencies. This skill provides a safe, manifest-driven mechanism to revert entire phases or plans while ensuring dependency integrity.

Core Features & Use Cases

  • Phase-based revert with dependency checks: Reverts entire phases defined in a manifest only if dependencies are satisfied.
  • Plan-based revert: Reverts all commits associated with a specific plan.
  • Interactive last N: Shows recent GSD commits for user selection.
  • Confirmation gate: Requires explicit user confirmation before performing the revert.
  • Auditable actions: Logs all revert actions for traceability.

Quick Start

Invoke the gsd-undo skill with the desired mode and confirm the revert before applying changes.

Frequently Asked Questions about gsd-undo

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

FAQPage Schema
How do I revert multiple git commits associated with a specific plan safely?

To safely revert git commits by plan, use a manifest-driven mechanism with --plan NN-MM to target specific commits, validate dependencies, and require explicit user confirmation before executing the undo.

What is phase-aware git revert and how does it handle dependencies?

Phase-aware git revert uses a phase manifest to revert entire phases only when dependency checks are satisfied, performing dry runs if possible and logging actions for audit trails.

Can I undo recent git changes without specifying a phase or plan?

Yes, you can undo recent git changes using the --last N mode, which interactively shows recent GSD commits for user selection before applying the revert through a confirmation gate.

Does this manifest-driven revert approach work with standard git workflows?

Yes, the manifest-driven revert integrates with standard git workflows by validating phase dependencies, running dry runs if possible, and logging all undo actions for audit traceability.

What are the limitations of reverting git phases with dependency checks?

Reverting git phases with dependency checks is limited by dependency integrity; the phase revert will not proceed unless dependencies are satisfied, and it requires explicit user confirmation alongside a valid phase manifest.