conductor-revert
Lets your agent undo code changes intelligently. It can revert logical work units, like phases or tasks.
What it does
This tool helps you undo changes in your code in an organized way. It allows you to revert specific parts of your work, like a task, a phase, or an entire project, using Git history.
When to use it
- ✓When you need to undo a specific change without messing up the history.
- ✓If you want to revert a part of the project to a previous state.
- ✓To fix a mistake by undoing the last changes made.
Example of what to ask your AI
“Undo task 2.3 from the 'auth_20250115' project.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool checks if your project is ready to undo changes, looks at the Git history to find the correct changes, and asks for your confirmation before undoing them.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill conductor-revertOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/conductor-revert/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Revert Track
Revert changes by logical work unit with full git awareness. Supports reverting entire tracks, specific phases, or individual tasks.
Use this skill when
- Working on revert track tasks or workflows
- Needing guidance, best practices, or checklists for revert track
Do not use this skill when
- The task is unrelated to revert track
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
Pre-flight Checks
Verify Conductor is initialized:
- Check
conductor/tracks.mdexists - If missing: Display error and suggest running
/conductor:setupfirst
- Check
Verify git repository:
Run
git statusto confirm git repoCheck for uncommitted changes
If uncommitted changes exist:
WARNING: Uncommitted changes detected Files with changes: {list of files} Options: 1. Stash changes and continue 2. Commit changes first 3. Cancel revert
Verify git is clean enough to revert:
- No merge in progress
- No rebase in progress
- If issues found: Halt and explain resolution steps
Target Selection
If argument provided:
Parse the argument format:
Full track: {trackId}
- Example:
auth_20250115 - Reverts all commits for the entire track
Specific phase: {trackId}:phase{N}
- Example:
auth_20250115:phase2 - Reverts commits for phase N and all subsequent phases
Specific task: {trackId}:task{X.Y}
- Example:
auth_20250115:task2.3 - Reverts commits for task X.Y only
If no argument:
Display guided selection menu:
What would you like to revert?
Currently In Progress:
1. [~] Task 2.3 in dashboard_20250112 (most recent)
Recently Completed:
2. [x] Task 2.2 in dashboard_20250112 (1 hour ago)
3. [x] Phase 1 in dashboard_20250112 (3 hours ago)
4. [x] Full track: auth_20250115 (yesterday)
Options:
5. Enter specific reference (track:phase or track:task)
6. Cancel
Select option:
Commit Discovery
For Task Revert
Search git log for task-specific commits:
git log --oneline --grep="{trackId}" --grep="Task {X.Y}" --all-matchAlso find the plan.md update commit:
git log --oneline --grep="mark task {X.Y} complete" --grep="{trackId}" --all-matchCollect all matching commit SHAs
For Phase Revert
Determine task range for the phase by reading plan.md
Search for all task commits in that phase:
git log --oneline --grep="{trackId}" | grep -E "Task {N}\.[0-9]"Find phase verification commit if exists
Find all plan.md update commits for phase tasks
Collect all matching commit SHAs in chronological order
For Full Track Revert
Find ALL commits mentioning the track:
git log --oneline --grep="{trackId}"Find track creation commits:
git log --oneline -- "conductor/tracks/{trackId}/"Collect all matching commit SHAs in chronological order
Execution Plan Display
Before any revert operations, display full plan:
================================================================================
REVERT EXECUTION PLAN
================================================================================
Target: {description of what's being reverted}
Commits to revert (in reverse chronological order):
1. abc1234 - feat: add chart rendering (dashboard_20250112)
2. def5678 - chore: mark task 2.3 complete (dashboard_20250112)
3. ghi9012 - feat: add data hooks (dashboard_20250112)
4. jkl3456 - chore: mark task 2.2 complete (dashboard_20250112)
Files that will be affected:
- src/components/Dashboard.tsx (modified)
- src/hooks/useData.ts (will be deleted - was created in these commits)
- conductor/tracks/dashboard_20250112/plan.md (modified)
Plan updates:
- Task 2.2: [x] -> [ ]
- Task 2.3: [~] -> [ ]
================================================================================
!! WARNING !!
================================================================================
This operation will:
- Create {N} revert commits
- Modify {M} files
- Reset {P} tasks to pending status
This CANNOT be easily undone without manual intervention.
…
FAQ
What happens if I have uncommitted changes?
The tool will warn you and ask if you want to temporarily save these changes (stash), save them permanently (commit), or cancel the operation.
What are 'tracks', 'phases', and 'tasks'?
These are ways to organize work. 'Track' is the entire project, 'phase' is a larger stage within the project, and 'task' is a smaller job within a phase.
What if a conflict occurs during the revert?
The tool will stop and notify you about the conflict, showing which files were affected. It doesn't try to resolve it automatically and gives you options to proceed or cancel.
Details
Original description by the author
Git-aware undo by logical work unit (track, phase, or task)
Popularity
- GitHub stars
- 48k
- Ranking position
- #2619
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC