flywheel-rollback

Reverts a completed bead implementation using git revert and restores its open status.

3|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-rollback-burningportra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flywheel-rollback
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/flywheel-rollback
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-rollback-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a completed bead turns out to be buggy, unwanted, or implemented incorrectly, you need a safe way to undo its changes without losing the bead's tracking state. This Skill rolls back a bead's commits and reopens it for re-implementation. ## Core Features & Use Cases - Guided Commit Selection: Lists completed beads via br list --json and shows recent commits with git log --oneline so you can pinpoint where the bead's work began. - Safe Revert Workflow: Uses git revert (single commit or range) instead of destructive resets, with an explicit user confirmation before any changes are made. - State Synchronization: Updates the bead status back to open, removes it from checkpoint beadResults, and cancels the associated task so the flywheel can re-implement it cleanly. - Use Case: After a review reveals a bead introduced a regression, roll it back, reopen the bead, and let the flywheel re-implement it with corrected guidance. ## Quick Start Ask the assistant to roll back bead bd-42 and confirm the revert when prompted.

Frequently Asked Questions about flywheel-rollback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I roll back a completed bead in agent-flywheel?

Invoke the rollback skill with an optional bead ID. It lists completed beads, shows recent commits, asks which commit starts the bead, then reverts the changes and reopens the bead after your confirmation.

Does the rollback use git reset or git revert?

It uses git revert, either for a single commit or a commit range, and explicitly prefers revert over reset. This preserves history and avoids destructive rewriting of shared commits.

What happens to the bead status after a rollback?

The bead is set back to open via `br update <id> --status open`, removed from the checkpoint's beadResults, and its associated task is marked deleted so it can be re-implemented.

Can I roll back a bead without knowing its ID?

Yes. If no bead ID is provided, the skill runs `br list --json` and presents completed beads for you to choose from before proceeding with the revert.

Is the rollback operation confirmed before changes are made?

Yes. The skill asks you to identify the starting commit and then explicitly asks for confirmation that changes will be reverted before executing any git revert command.