Conductor Revert (Git-aware Revert Track)

What it does

Provides a verified, provenance-preserving revert workflow for codebases organized into 'tracks' and 'tasks'. The skill discovers commits for a target (task/phase/track), builds an explicit revert execution plan (commits to revert, files affected), enforces pre-flight checks (clean git state, no rebase/merge, provenance review), and requires explicit confirmation before making any changes. It emphasizes safety: never force-push, never auto-resolve conflicts, and halt on any unexpected condition.

When to use it

Use when you need to undo work by logical unit (single task, phase, or entire track) and must preserve upstream provenance and support files. Ideal for repository maintainers, reviewers, or operators who need auditable revert operations with clear verification steps. Do NOT use for generic undo tasks where provenance or safety controls are unnecessary.

What's included

• Scripts: None detected in intake (has_scripts=false)
• References: ORIGIN.md and metadata.json are expected for provenance
• Instructions: Detailed pre-flight checks, commit-discovery strategies, execution-plan display, stepwise revert sequence, conflict handling, and post-revert verification (plan.md updates).

Compatible agents

{}