maestro:revert

To revert a Git commit and reset plan state, this Skill utilizes `git revert` to create undo commits while updating `plan.md` to roll back task completion status. It targets specified tracks, phases, or tasks to ensure your project plan accurately reflects the reverted work.

The safest way to undo Git implementation work without losing history is using `git revert` to generate new commits that undo previous ones. This approach preserves your commit history while rolling back the unwanted changes and resetting the project plan state.

Yes, you can revert code changes at the track, phase, or individual task level. This granular reversion capability allows you to target specific sections of your development workflow, undoing only the relevant Git commits and resetting the corresponding plan.md status.

Yes, reverting commits includes mandatory pre-flight safety checks and creates backup tags before executing the undo operations. These precautions prevent destructive actions and data loss, while a clear decision tree guides the safe rollback of both Git state and plan.md updates.

Rolling back plan state is necessary when undoing Git commits because it resets task completion status in `plan.md` to match the reverted code. Without this synchronization, your development orchestrator would incorrectly mark undone work as complete, causing workflow tracking errors.

You should avoid using git revert if you need to completely erase a commit from history rather than appending an undo commit. This Skill focuses on safe, non-destructive reversion; if pre-flight safety checks fail or backup tags cannot be created, the rollback operation is aborted to prevent data loss.