ll-cleanup-worktrees

Identify and remove orphaned git worktrees from local repositories.

7|2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-cleanup-worktrees
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ll-cleanup-worktrees
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/skills/ll-cleanup-worktrees
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-cleanup-worktrees

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the clutter and potential conflicts caused by orphaned git worktrees that remain on your filesystem after an interrupted ll-parallel execution.

Core Features & Use Cases

  • Orphaned Worktree Detection: Automatically identifies git worktrees that are no longer associated with an active loop process.
  • Safe Cleanup: Removes stale directories to reclaim disk space and prevent git branch locking issues.
  • Use Case: If a parallel sprint execution crashes or is terminated prematurely, use this skill to restore your repository to a clean state before starting a new task.

Quick Start

Ask the agent to clean up any orphaned git worktrees left behind by previous parallel runs.

Frequently Asked Questions about ll-cleanup-worktrees

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

FAQPage Schema
How do I clean up orphaned git worktrees left after a crashed parallel execution?

To clean up orphaned git worktrees, you need to identify stale directories and execute git-native cleanup commands. This removes abandoned worktree artifacts, preventing branch locking issues and reclaiming disk space.

What are orphaned git worktrees and why do they cause repository issues?

Orphaned git worktrees are stale directories remaining on your filesystem after an interrupted parallel task execution. They cause repository issues by interfering with branch management, locking branches, and wasting disk utilization.

How do I remove stale worktrees to restore my local repository to a clean state?

You can remove stale worktrees by targeting local repository environments and executing git cleanup commands. This safe cleanup process ensures the repository state remains consistent and free of abandoned artifacts.

Can I use git worktree cleanup for local repositories affected by interrupted task execution?

Yes, you can use git worktree cleanup for local repositories affected by interrupted task execution. The cleanup process targets local environments to automatically identify and remove worktrees no longer associated with active loop processes.

What happens if I do not purge abandoned git worktree artifacts before starting a new task?

If you do not purge abandoned git worktree artifacts, stale directories will remain on your filesystem. This leads to git branch locking issues, inconsistent repository state, and reduced disk utilization before starting a new task.