conductor-revert

Reverts git commits by logical work unit such as track, phase, or task.

2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/monang404/lunawave --skill conductor-revert-monang404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conductor-revert
Source: https://github.com/monang404/lunawave/tree/main/.agent/skills/conductor-revert
Command: npx skills add https://github.com/monang404/lunawave --skill conductor-revert-monang404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Undoing work in a git repository is risky when commits span multiple tasks and phases. This Skill reverts changes by logical work unit instead of raw commit hashes, keeping history intact and plan files synchronized. ## Core Features & Use Cases - Granular Revert Targets: Revert an entire track, a specific phase, or a single task using references like trackId:phase2 or trackId:task2.3. - Safe Execution Workflow: Discovers related commits via git log, shows a full execution plan, and requires explicit 'YES' confirmation before running git revert. - Plan Synchronization: Automatically resets task markers in plan.md and tracks.md after reverting, and halts immediately on merge conflicts for manual resolution. - Use Case: A task implementation introduced a bug after being marked complete. Revert just that task's commits, reset its status to pending, and keep all other work untouched. ## Quick Start Ask the assistant to revert task 2.3 in track dashboard_20250112 using the conductor-revert skill.

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?▼

Provide a task reference like trackId:task2.3 and the skill searches git log for commits matching that track and task, then runs git revert on them in reverse chronological order. It also resets the task marker in plan.md to pending.

How to undo a full feature track without git reset?▼

Pass the track ID alone to revert every commit associated with that track using git revert, which preserves history instead of rewriting it. The skill never uses git reset --hard or force push, so the operation stays safe for shared remotes.

What happens if a git revert causes a merge conflict?▼

The skill halts immediately on any conflict and lists the conflicted files with options to show details, abort the sequence, or view a manual resolution guide. It never attempts automatic conflict resolution.

Can I revert commits that were already pushed to a remote?▼

Yes. The skill warns when target commits exist on the remote and explains that git revert creates new commits you push normally, avoiding any force push. You confirm with YES before it proceeds.

What are the limitations of reverting by work unit?▼

Commit discovery depends on commit messages containing the track ID and task numbers, so commits with different formats may be missed. Tracks with no matching commits cannot be reverted, only their directories deleted.