conductor-revert

To revert code changes and keep Conductor documentation synchronized, this Skill maps Conductor items to Git commit SHAs, executes the code rollback, and updates plan.md or tracks.md to prevent documentation drift.

Undoing a completed task safely requires analyzing git history to find the corresponding commit, presenting a revert plan for confirmation, and executing a rollback that synchronizes Conductor artifacts like plan.md.

Yes, you can revert specific phases or tasks individually by mapping targeted Conductor items to their exact Git commit SHAs, allowing you to undo precise logical units of work rather than broad code changes.

Yes, the Conductor revert process handles git conflicts during a code rollback by presenting a detailed revert plan for confirmation before safely executing the rollback and managing any conflicts that arise.

To update plan.md after reverting a task, the Skill automatically synchronizes Conductor documentation artifacts during the code rollback, ensuring the plan accurately reflects the undone state without manual edits.