gsd-undo

To safely revert Git commits for a project phase, use a rollback tool with dependency checks and confirmation gates. This ensures phase-specific reverts maintain code integrity and prevent unintended changes by validating dependencies before execution.

The best way to roll back multiple Git commits without breaking dependencies is using a rollback mechanism that resolves dependencies via a phase manifest. This approach checks dependencies interactively before reverting, ensuring safe commit rollback across the project.

Yes, you need a phase manifest to perform a plan-specific commit rollback. The manifest is explicitly required for dependency resolution, allowing the rollback process to safely identify and revert all commits associated with that specific plan.

Interactive commit selection during a Git revert works by displaying recent commits for user selection. Instead of automatically rolling back, it shows recent project commits, allowing you to interactively choose specific commits to revert safely.

Yes, you can revert the last few commits in your current development phase by specifying the number of commits to undo. This reverts the specified number of recent commits safely with built-in dependency checks and confirmation gates.