revert-track

Revert related git commits as a single history-safe operation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/escotilha/claude-public --skill revert-track
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revert-track
Source: https://github.com/escotilha/claude-public/tree/main/skills/revert-track
Command: npx skills add https://github.com/escotilha/claude-public --skill revert-track

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about revert-track

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

FAQPage Schema
How do I revert multiple commits for a single feature in git safely?

To revert a feature safely, this skill locates all related commits for a logical unit of work and executes a single git revert operation. This preserves your git history while undoing the broken track as one clean rollback commit.

What is the best way to undo a parallel development track without losing git history?

Undoing a parallel development track safely requires reading `.parallel-dev-state.json` to identify all related commits, then applying a single git revert. This rolls back the feature while keeping your overall git timeline intact and clean.

Can I do a dry run before reverting a deep-plan implementation phase in git?

Yes, you can perform a dry run before reverting a deep-plan implementation phase by using the `--dry-run` flag. This inspects exactly which commits and files from `.deep-plan-state.json` would be reverted before any destructive actions occur.

How do I check for conflict risk before rolling back a feature track?

To check for conflict risk before a rollback, the skill assesses post-track modifications to affected files. It identifies potential conflicts by detecting changes made after the target feature track, ensuring a safe revert operation.

How do I revert a manual range of commits when a feature breaks production?

To revert a manual range of commits when a feature breaks production, you can specify a custom commit range instead of relying on state files. The skill applies the revert as a single git operation to restore stability.