deep-cleanup

Remove stale deep loop session artifacts older than 7 days.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/marcusgoll/deep-loop-plugin --skill deep-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-cleanup
Source: https://github.com/marcusgoll/deep-loop-plugin/tree/main/skills/deep-cleanup
Command: npx skills add https://github.com/marcusgoll/deep-loop-plugin --skill deep-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stale deep loop session files including old .deep directories, outdated plan files, orphaned lock files, and stuck escalation files clutter your development workspace and can cause errors when starting new deep loop sessions.

Core Features & Use Cases

  • Stale Directory Cleanup: Automatically removes .deep directories older than 7 days to free up disk space.
  • Plan File Pruning: Deletes outdated plan files from ~/.claude/plans/ that are no longer needed.
  • Lock & Escalation Reset: Clears orphaned agent lock files and resets stuck escalation files to unblock stuck sessions.
  • Use Case: Run this skill after abandoning a deep loop session, before starting a new project, or when your session-start hook reports stale directory warnings.

Quick Start

Use the deep-cleanup skill to remove all stale deep loop session artifacts from your current project.

Frequently Asked Questions about deep-cleanup

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

FAQPage Schema
How do I clean up stale deep loop session artifacts and directories?

To clean up stale deep loop session artifacts, you can automatically remove outdated .deep directories, old plan files, orphaned lock files, and stuck escalation files. This process targets temporary development session artifacts older than 7 days to free up disk space.

Why does my session-start hook report stale directory warnings?

Your session-start hook reports stale directory warnings because old .deep directories from previous development sessions are still present. Removing these stale directories resolves the warnings and prepares your workspace for a new deep loop session.

What is the best way to unblock stuck deep loop sessions caused by orphaned files?

The best way to unblock stuck deep loop sessions is to reset orphaned agent lock files and clear stuck escalation files. This removes the conflicting session artifacts that prevent new processes from starting.

When should I purge outdated plan files from my development workspace?

You should purge outdated plan files from ~/.claude/plans/ after abandoning a deep loop session or before starting a fresh project. This removes unneeded temporary development session artifacts and prevents workspace clutter.

Are there age thresholds for deleting .deep directories and plan files?

Yes, there are deterministic file deletion requirements that apply a 7-day age threshold for .deep directories and plan files. This ensures only old temporary development session artifacts are removed during cleanup.