flow-reset

Remove FLOW worktrees, branches, state files, and PRs from a project.

25|3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/benkruger/flow --skill flow-reset
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-reset
Source: https://github.com/benkruger/flow/tree/main/skills/flow-reset
Command: npx skills add https://github.com/benkruger/flow --skill flow-reset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove FLOW artifacts from the current project to restore a clean baseline by clearing worktrees, branches, state files, and PRs.

Core Features & Use Cases

  • Inventory and enumerate FLOW artifacts across worktrees, state files, start-queue, local and remote branches, and open PRs.
  • Safely execute a complete reset sequence: close PRs, remove worktrees, delete remote/local branches, clear state files and lock queues.
  • Confirm before destructive actions and verify post-reset state.

Quick Start

Run flow-reset on a repository to purge all FLOW artifacts from the current project.

Frequently Asked Questions about flow-reset

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

FAQPage Schema
How do I clean up abandoned git worktrees and branches from stale experiments?

To purge stale experiments, you must remove git worktrees, local and remote branches, state files, and open PRs. A complete reset sequence inventories all artifacts before removal to guarantee a clean baseline.

What is the best way to reset a project and remove all open PRs and state files?

The best way to reset a project and remove open PRs and state files is to run an automated purge that closes PRs, deletes remote and local branches, and clears lock queues. This verifies the post-reset state for safety.

Can I safely delete remote branches and worktrees without affecting the main branch?

Yes, you can safely delete remote branches and worktrees without affecting the main branch by using a purge process that includes main-branch protection and confirmation prompts. It verifies the post-reset state after removal.

Does the git cleanup process require confirmation before deleting branches and PRs?

Yes, the git cleanup process requires confirmation before executing destructive actions like deleting branches and closing PRs. This safeguard ensures you explicitly approve the removal of worktrees, state files, and lock queues.

When should I not use an automated artifact removal tool for my git repository?

You should not use automated artifact removal when you need to retain active feature branches, open pull requests, or in-progress state files. The tool performs a complete reset, permanently purging all associated worktrees and queues.