conductor-revert

To revert a track or phase in a Git repository, this skill identifies all associated implementation and plan-update commits, including those in non-linear histories, and executes a revert after explicit user confirmation.

Yes, you can undo commits with rewritten or merge histories. The skill reconciles non-linear Git histories to accurately identify the real-world commits associated with the logical units of work you want to revert.

Yes, the git revert process requires explicit user confirmation before executing any actions. This validation step ensures you can safely undo work without accidental changes to your project history.

The best way to undo logical units of work tracked by Conductor is to target the specific track, phase, or task. The skill identifies the corresponding Git commits and reverts them while validating tool call success.

Reverting a Conductor track keeps your project history clean by identifying and undoing specific implementation and plan-update commits. It handles complex histories to ensure the revert accurately targets the intended work.

You should not use an automated git revert if you cannot provide explicit confirmation for the identified commits. The skill relies on user validation to prevent accidental changes before executing any revert actions on your history.