flow-complete

Merge a PR, clean up worktrees, and render a completion summary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalizes a feature by merging the PR, removing the worktree, and deleting the per-branch state file, while producing a complete post-merge summary and artifacts.

Core Features & Use Cases

  • Finalize merge: perform the merge, close out related checks, and update the PR state.
  • Cleanup: remove local worktrees, delete the state file, and render the complete banner and artifact summary.
  • Idempotent multi-branch readiness: supports concurrent finalizations and safe re-invocation.

Quick Start

Run /flow:flow-complete on your feature branch to initiate all finalization steps.

Frequently Asked Questions about flow-complete

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

FAQPage Schema
How do I automate PR merge and worktree cleanup after finishing a feature?

Idempotent feature finalization allows safe re-invocation, meaning you can run the merge and cleanup process again without duplicating actions or corrupting the state file, ensuring concurrent multi-branch finalizations remain safe.

What is the best way to finalize merges in a multi-branch project safely?

Post-merge cleanup removes the local worktree, deletes the associated state file, and renders a complete banner with artifact summaries, ensuring no residual local branches or tracking files remain after the feature is finalized.

Does feature finalization work with existing CI checks and PR state updates?

Feature finalization tracks progress using per-branch state files stored under the .flow-states directory, which are safely deleted during the cleanup phase after the merge and artifact summary are successfully completed.

Why do I need a state file for post-merge worktree cleanup?

Feature finalization closes out related CI checks and updates the PR state during the merge process, ensuring the continuous integration pipeline fully completes before local worktrees and state files are removed.

Can I re-run post-merge cleanup safely if the finalization process fails midway?

You need a per-branch state file to support idempotent multi-branch readiness, allowing the finalization process to safely re-invoke, track concurrent merges, and accurately clean up the correct worktrees without data loss.