revert-track

What problem does it solve?

Reverting a broken feature manually can be risky and time-consuming because it may require identifying many related commits and preserving a clean history.

Core Features & Use Cases

• Track-based commit discovery: Locates all commits belonging to a logical unit of work using state files from parallel-dev and deep-plan or by commit-range input.
• Single-operation history-safe revert: Performs a clean git revert of all identified commits as one undo commit (preserving history).
• Safety guardrails: Offers --dry-run, shows what will be reverted, and assesses conflict risk by detecting post-track modifications to affected files.
• Practical examples: Use it to roll back a failing feature to restore production stability, or to undo a deep-plan implementation phase without losing the overall git timeline.

Quick Start

Run: /revert-track auth --dry-run to inspect exactly which commits and files would be reverted for the auth track before making any changes.