conductor-revert
Conductor Revert
Overview
This skill is a Git-aware assistant. Unlike a standard git revert, it understands the relationship between implementation commits and the Conductor documentation. It ensures that when code is reverted, the corresponding plan.md and tracks.md files are also reset to their previous states.
It is designed to handle common non-linear Git histories, such as rewritten commits (from rebase/squash) and merge commits, with robust "Ghost" commit detection and plan-update commit association.
When to Use
- When a user says "Undo that task," "Revert the last phase," or "I want to delete this track and its changes."
- To cleanly roll back a feature that isn't working as expected.
Workflow
The revert process follows 4 phases:
Phase 1: Interactive Target Selection & Confirmation
More from airclear/skills
bmad-tea
Enterprise Test Architecture (TEA) framework for quality engineering. Includes workflows for testing education (TEA Academy), risk-based test design, framework scaffolding, ATDD (Red-phase), CI/CD pipeline configuration, NFR (Non-functional) assessment, and quality auditing (0-100 scoring). Use for establishing or executing comprehensive testing strategies.
14conductor-setup
Scaffolds the project and sets up the Conductor environment for Context-Driven Development. Use when starting a new project or initializing the Conductor workflow in an existing (brownfield) project. This skill guides the user through project discovery, product definition, tech stack configuration, and initial track planning.
14conductor-status
Provides a comprehensive status overview of the Conductor project. Use when the user wants to know the current progress, active tasks, next steps, or overall health of the project tracks and plans.
12conductor-implement
Executes the tasks defined in a specified track's plan. Use when the user wants to start or continue implementing a feature or bug fix. This skill manages the task lifecycle, adheres to the project's workflow, synchronizes project documentation upon completion, and offers track cleanup options.
11conductor-review
Acts as a Principal Software Engineer and Code Review Architect to review completed or in-progress work against project standards, style guides, and the implementation plan. Use when the user wants a quality check on their code or before finalizing a track.
10conductor-newtrack
Initiates a new unit of work (Track) in a Conductor-managed project. Use when the user wants to start a new feature, fix a bug, or perform maintenance. This skill guides the user through interactive specification building and detailed implementation planning.
9