conductor-revert
Revert git changes by logical work unit
Safely undo git commits by track, phase, or task with full history preservation. This skill provides structured revert workflows with explicit confirmation and conflict detection.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "conductor-revert". Revert task 2.3 in auth_20250115
Expected outcome:
REVERT EXECUTION PLAN
Target: Task 2.3 in auth_20250115
Commits to revert (in reverse chronological order):
1. abc1234 - feat: add OAuth callback handler (auth_20250115)
2. def5678 - chore: mark task 2.3 complete (auth_20250115)
Files that will be affected:
- src/auth/oauth.ts (will be deleted)
- src/routes/callback.ts (will be deleted)
- conductor/tracks/auth_20250115/plan.md (modified)
Plan updates:
- Task 2.3: [~] -> [ ]
!! WARNING !!
This operation will:
- Create 2 revert commits
- Modify 3 files
- Reset 1 task to pending status
Type 'YES' to proceed, or anything else to cancel:
Using "conductor-revert". Revert phase 1 in dashboard_20250112
Expected outcome:
REVERT EXECUTION PLAN
Target: Phase 1 in dashboard_20250112 (Tasks 1.1 through 1.4)
Commits to revert (in reverse chronological order):
1. ghi9012 - feat: add dashboard export (dashboard_20250112)
2. jkl3456 - chore: mark task 1.4 complete (dashboard_20250112)
3. mno7890 - feat: add chart filters (dashboard_20250112)
4. pqr1234 - chore: mark task 1.3 complete (dashboard_20250112)
5. stu5678 - feat: add data hooks (dashboard_20250112)
6. vwx9012 - chore: mark task 1.2 complete (dashboard_20250112)
7. yza3456 - feat: add chart rendering (dashboard_20250112)
8. bcd7890 - chore: mark task 1.1 complete (dashboard_20250112)
Type 'YES' to proceed, or anything else to cancel:
Security Audit
SafeAll 59 static analysis findings are false positives. The detected 'external_commands' patterns are Markdown documentation examples, not executable code. The skill describes safe git revert operations with explicit safety rules forbidding dangerous commands like git reset --hard and git push --force. Requires explicit user confirmation before any changes.
Risk Factors
⚙️ External commands (54)
Quality Score
What You Can Build
Undo a failed feature implementation
Revert all commits for a specific task that introduced bugs or did not meet requirements
Restore previous working state
Revert an entire phase of work to return to a known good state before a major refactor
Clean up experimental work
Remove all traces of an experimental track that was not merged to production
Try These Prompts
Revert task 2.3 in the auth_20250115 track. Show me what commits will be affected and confirm before proceeding.
Revert phase 2 of the dashboard_20250112 track. I want to see the full plan with all affected files before confirming.
Help me revert some recent work. Show me the available tracks and tasks I can revert.
Revert the entire experiment_20250120 track. This experimental feature was not approved and needs to be fully removed from history.
Best Practices
- Always review the full execution plan before confirming any revert operation
- Run tests after revert completion to verify the application works correctly
- Communicate with your team before reverting shared or reviewed work
Avoid
- Do not use this skill to hide mistakes from team members - discuss issues openly
- Avoid reverting work that others have built upon without coordination
- Do not skip the explicit confirmation step - always review the plan first