revert

Revert Git commits and synchronize track-state.json and plan.md markers.

Updated May 7, 2026

Search Tags:#automation #git #workflow #conductor #state-management #revert

Ready to run

npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill revert-ataraxiaepiphany

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: revert
Source: https://github.com/AtaraxiaEpiphany/conductor/tree/main/skills/revert
Command: npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill revert-ataraxiaepiphany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent project states that occur when manually reverting code in a framework that relies on strict state tracking, such as Conductor.

Core Features & Use Cases

Atomic State Synchronization: Automatically updates track-state.json and plan.md markers to match the reverted Git history.
Multi-Level Reversion: Supports reverting individual tasks, entire phases, or complete tracks with full dependency awareness.
Safety Guardrails: Enforces pre-action checks and requires user confirmation to prevent accidental data loss or state corruption.

Quick Start

Use the revert skill to undo the most recent task implementation and synchronize the project state.

Frequently Asked Questions about revert

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

FAQPage Schema

How do I revert a Git commit without breaking Conductor state tracking?▼

To revert a Git commit without breaking Conductor state tracking, you need an atomic reversion process that reconciles Git history with track-state.json and plan.md markers simultaneously. This ensures project state markers match the reverted code.

What happens to plan.md markers when I undo a task implementation in Conductor?▼

When undoing a task implementation in Conductor, atomic state synchronization automatically updates plan.md markers and track-state.json to match the reverted Git history, preventing inconsistent project states and state corruption.

Can I revert an entire phase or track in Conductor instead of just one task?▼

Yes, you can revert an entire phase or track in Conductor instead of just one task. Multi-level reversion supports reverting individual tasks, complete phases, or full tracks with full dependency awareness.

Do I need the track-state CLI to perform atomic Git reverts in Conductor?▼

Yes, you need the track-state CLI to perform atomic Git reverts in Conductor. The CLI is required alongside Git to execute atomic state resets and perform validation checks during the reversion process.

How to prevent state corruption when rolling back code in a state-aware workflow?▼

To prevent state corruption when rolling back code in a state-aware workflow, use safety guardrails that enforce pre-action checks and require user confirmation. This stops accidental data loss during atomic state resets.