Revert Track

Revert changes by logical work unit with full git awareness. Supports reverting entire tracks, specific phases, or individual tasks.

Use this skill when

• •Working on revert track tasks or workflows
• •Needing guidance, best practices, or checklists for revert track

Do not use this skill when

• •The task is unrelated to revert track
• •You need a different domain or tool outside this scope

Instructions

• •Clarify goals, constraints, and required inputs.
• •Apply relevant best practices and validate outcomes.
• •Provide actionable steps and verification.
• •If detailed examples are required, open resources/implementation-playbook.md.

Pre-flight Checks

1. •

   Verify Conductor is initialized:

   • •Check conductor/tracks.md exists
   • •If missing: Display error and suggest running /conductor:setup first
2. •

   Verify git repository:

   • •

     Run git status to confirm git repo

   • •

     Check for uncommitted changes

   • •

     If uncommitted changes exist:

     code

     WARNING: Uncommitted changes detected
     
     Files with changes:
     {list of files}
     
     Options:
     1. Stash changes and continue
     2. Commit changes first
     3. Cancel revert
     

3. •

   Verify git is clean enough to revert:

   • •No merge in progress
   • •No rebase in progress
   • •If issues found: Halt and explain resolution steps

Target Selection

🧠 Knowledge Modules (Fractal Skills)

1. If argument provided:

2. If no argument:

3. For Task Revert

4. For Phase Revert

5. For Full Track Revert

6. On Merge Conflict

7. If reverting entire track:

8. If reverting to incomplete state:

9. Track Never Committed

10. Commits Already Reverted

11. Remote Already Pushed