Verified:GitHub

flow-abort

Abort the current FLOW feature by closing the PR, deleting the remote branch, removing the worktree, and deleting the state file.

25|3|Updated Feb 19, 2026

Search Tags:#devops #cleanup #worktree #flow #pull-request #abort #state-file

Ready to run

npx skills add https://github.com/benkruger/flow --skill flow-abort

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flow-abort
Source: https://github.com/benkruger/flow/tree/main/skills/flow-abort
Command: npx skills add https://github.com/benkruger/flow --skill flow-abort

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aborts the current FLOW feature gracefully by closing PRs, cleaning up worktrees, and removing per-feature state to prevent drift.

Core Features & Use Cases

Close the in-flight feature by closing the PR and deleting the remote branch.
Remove the worktree and state files, preserving repository hygiene.
Safe, multi-mode operation with auto and manual confirmation, plus safeguards and reporting.

Quick Start

Abort the current FLOW feature from any phase and perform cleanup using the configured mode.

Frequently Asked Questions about flow-abort

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

FAQPage Schema

How do I safely abort a pull request and clean up the worktree?▼

To safely abort a pull request and clean up the worktree, an automated flow abort process closes the PR, deletes the remote branch, removes the worktree, and deletes the state file. This ensures repository hygiene and prevents drift.

What is the best way to delete a remote branch and remove local state files together?▼

The best way to delete a remote branch and remove local state files together is a graceful flow abort. This integrated cleanup closes in-flight features, removes the worktree, and deletes per-feature state to prevent configuration drift.

How does automated confirmation work when aborting a devops feature flow?▼

Automated confirmation when aborting a devops feature flow works by consulting a per-branch state file. If the mode is unspecified, it defaults to auto to safely close the PR, remove the worktree, and delete the state file without manual prompts.

Can I abort a feature flow from any phase of development?▼

Yes, you can abort a feature flow from any phase of development. The abort process safely closes the PR, deletes the remote branch, removes the worktree, and deletes the state file regardless of the current development stage.

Why should I remove worktrees and state files when closing a pull request?▼

You should remove worktrees and state files when closing a pull request to preserve repository hygiene and prevent drift. Aborting the flow gracefully cleans up these per-feature artifacts alongside the remote branch deletion.