cancel-refine-loop

To cancel an active refine loop in Claude, you remove the state files from the .claude/refine-loop/ directories. This skill detects active quality improvement cycles and prompts you to confirm cancellation of all or specific loop types before deleting them.

The best way to stop a running quality improvement cycle without leaving partial state behind is to delete the corresponding state directories. This ensures cleanup of related state files to prevent resumption of stale loops.

State management for canceling refine loops works by detecting active loops across code, tests, UI tests, and skills. It then prompts you to select specific types to cancel and deletes the corresponding .claude/refine-loop/ directories.

Yes, you can select specific loop types to cancel instead of stopping all active refine loops. The skill provides user prompts allowing you to confirm cancellation of all loops or choose specific categories like code or UI tests.

A stale refine loop resumes when partial state files remain in the .claude/refine-loop/ directories. You prevent it in your DevOps automation by using this skill to ensure complete cleanup of related state files after stopping the cycle.

No, you do not need any dependencies to clear refine loop state files. The skill operates independently to detect active loops and delete their corresponding directories without requiring external components.