tidy

Stop processes, remove session worktrees, and reset linked CLIs to main checkout.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wind down transient state from a development session by stopping background processes, removing worktrees for merged branches, repointing linked CLIs back at the main checkout, and deleting merged branches locally and on the remote. This helps return the machine to a clean baseline after a feature lands.

Core Features & Use Cases

  • Stop background tasks started during a session to free resources and improve stability.
  • Remove session-created worktrees and re-link CLIs to the main checkout, ensuring the environment is clean for subsequent work.
  • Safely prune merged local branches and optionally remote branches with explicit user confirmation to avoid disrupting teammates.

Quick Start

Run /tidy and confirm each action before it is executed.

Frequently Asked Questions about tidy

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

FAQPage Schema
How do I clean up git worktrees after finishing a development session?

You can clean up git worktrees by stopping background processes, removing session-created worktrees, and repointing linked CLIs to the main checkout. This returns your dev session to a clean baseline after a feature lands.

What is the best way to delete merged git branches locally and on the remote?

The best way to delete merged git branches is to prune them locally and optionally on the remote with explicit user confirmation. This prevents accidental data loss and avoids disrupting teammates during post-ship cleanup.

How do I stop background processes started during a development session?

To stop background processes started during a development session, you apply a cleanup routine that automatically detects and halts them. This frees system resources and improves stability before removing worktrees and branches.

Does git worktree cleanup require confirmation before deleting remote branches?

Yes, git worktree cleanup requires explicit user confirmation before any destructive or remote changes. This ensures you review and approve the deletion of merged branches locally and on the remote to avoid disrupting teammates.

When should I reset linked CLIs back to the main checkout?

You should reset linked CLIs back to the main checkout when returning a workspace to a known baseline after experiments, finishing a feature, or performing post-ship cleanup to ensure the environment is clean for subsequent work.