cleanup-sweep

Identify and manage stale, lost, or abandoned worktrees, branches, and stashes.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/souliane/teatree --skill cleanup-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup-sweep
Source: https://github.com/souliane/teatree/tree/main/skills/cleanup-sweep
Command: npx skills add https://github.com/souliane/teatree --skill cleanup-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires t3, workspace, rules, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying and managing stale, lost, or abandoned worktrees, branches, and stashes in a codebase, reducing manual cleanup tasks and preventing data loss.

Core Features & Use Cases

  • Identify Stale Items: Automatically detects and lists worktrees, branches, and stashes that are not actively being worked on.
  • Decide Action: Offers guidance on whether to salvage unmerged work to a fresh PR, delete redundant items, or keep uncertain ones with a warning.
  • Execute Actions: Safely deletes or salvages items based on the user's decisions.
  • Use Case: Use this Skill when you need to regularly clean up a repository and remove old work that is no longer needed.

Quick Start

To start the cleanup process, use the 'cleanup-sweep' skill. For example, 't3:cleanup-sweep'.

Frequently Asked Questions about cleanup-sweep

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

FAQPage Schema
How do I automate the cleanup of stale git worktrees and branches?

To automate stale worktree and branch cleanup, you can use this skill to scan your codebase and identify unused or outdated items. It detects abandoned worktrees, branches, and stashes, offering guidance on whether to delete redundant items or salvage unmerged work to a fresh PR.

What is the best way to manage abandoned stashes in a repository?

Managing abandoned stashes requires identifying those not actively in use and deciding whether to salvage or delete them. This skill detects stale stashes in your codebase, offering guidance to either keep uncertain items with a warning or safely delete redundant ones to maintain repository hygiene.

Do I need t3 and workspace overlays to identify stale repository items?

Yes, this skill requires t3 and related workspace overlays for effective repository management. These dependencies provide the necessary environment setup to identify and manage stale worktrees, branches, and stashes within your codebase.

How do I salvage unmerged work before deleting redundant branches?

To salvage unmerged work before deleting redundant branches, this skill evaluates stale items and recommends routing unmerged work to a fresh PR. You can then safely execute deletions for redundant branches while preserving valuable, unmerged changes.

When should I use an automated repository cleanup process?

You should use an automated repository cleanup process when you need to regularly remove old work that is no longer needed. This skill is designed for routine maintenance, helping you identify and manage stale, lost, or abandoned worktrees, branches, and stashes to reduce data loss risk.