conductor:revert

Revert git commits for selected Conductor Tracks, Phases, or Tasks.

8|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/cloudaura-io/cloudaura-marketplace --skill conductor-revert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conductor:revert
Source: https://github.com/cloudaura-io/cloudaura-marketplace/tree/main/plugins/conductor/skills/revert
Command: npx skills add https://github.com/cloudaura-io/cloudaura-marketplace --skill conductor-revert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reverts previous work using git-aware analysis to undo the logical units of work (Tracks, Phases, and Tasks) tracked by the Conductor framework.

Core Features & Use Cases

  • Interactive confirmation-driven revert of the exact commits that implement a selected Track, Phase, or Task.
  • Robust handling of non-linear Git histories, including rebases, squashes, and merges, with safeguards and auditability.
  • Generated, auditable execution plan that guides user through the revert process and ensures correctness.

Quick Start

Initiate the revert using the conductor:revert command and select a target (Track, Phase, or Task). The agent will guide you through confirmation, identify the relevant commits, present a reversible plan, and execute the reverts after your final approval.

Frequently Asked Questions about conductor:revert

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

FAQPage Schema
How do I revert commits for a specific task in git without breaking my history?

To revert commits for a specific task in git, you can use a git-aware assistant to identify the exact commits implementing that task and generate an auditable plan. This ensures your non-linear git history remains intact while safely undoing the logical unit of work.

Can I undo a git commit squash or merge safely if I lost track of the original changes?

Yes, you can undo changes from a git squash or merge safely by using a tool that resolves ghost commits and validates related implementation histories. It presents a reversible plan and requires explicit confirmation before executing the git revert actions.

What is the best way to undo a completed phase of work in a git-tracked project?

The best way to undo a completed phase of work in a git-tracked project is to target the specific phase through a git-aware revert process. It identifies the corresponding commits, prioritizes in-progress items, falls back to recently completed work, and requires final approval before reverting.

How does git revert work with complex non-linear histories when undoing a specific track?

Git revert with complex non-linear histories works by validating related implementation and plan commits to resolve ghost commits. It analyzes the history to find exact commits for the selected track, presenting an auditable execution plan that requires your final approval before performing any actions.

Do I need to manually find commits before reverting a task in a non-linear git history?

No, you do not need to manually find commits before reverting a task in a non-linear git history. The revert process automatically identifies and validates the exact commits corresponding to your selected task, handling rebases and merges while generating an auditable plan for your confirmation.