wtclean

Remove merged worktrees and branches from Git repositories.

15|1|Updated Oct 15, 2018
One-click install
npx skills add https://github.com/music-brain88/dotfiles --skill wtclean
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wtclean
Source: https://github.com/music-brain88/dotfiles/tree/main/.config/claude/skills/wtclean
Command: npx skills add https://github.com/music-brain88/dotfiles --skill wtclean

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, herdr, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of safely cleaning up worktrees and branches that have been merged into a repository, providing a streamlined way to manage the lifecycle of worktrees created with the '/wt' command.

Core Features & Use Cases

  • Safe Cleanup: Ensures that merged worktrees and branches are removed without affecting the integrity of the repository.
  • Dry Run Option: Allows users to preview the cleanup process before executing it.
  • Knowledge Extraction: Before deletion, extracts insights from the worktree logs to improve future processes.
  • Use Case: When a developer has merged a pull request, they can use this Skill to clean up the associated worktree, ensuring that the repository remains organized and that resources are freed up.

Quick Start

Run the 'wtclean' command to start the cleanup process.

Frequently Asked Questions about wtclean

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

FAQPage Schema
How do I clean up merged Git worktrees and branches after a pull request?

Git worktree logs are parsed to extract insights before deletion. This knowledge extraction improves future processes, ensuring that valuable worktree history is retained even after the branches are removed.

Can I preview a Git worktree cleanup before deleting branches?

Yes, you can perform a dry run to preview the cleanup process before executing it. This allows you to verify which merged worktrees and branches will be removed without making any actual changes to your repository.

Do I need GitHub CLI and Herdr to manage Git worktree lifecycles?

Git worktree logs are parsed to extract insights before deletion. This knowledge extraction improves future processes, ensuring that valuable worktree history is retained even after the branches are removed.

What is the best way to extract insights from Git worktree logs before deletion?

Yes, managing this specific worktree lifecycle requires Git, Herdr, and GitHub CLI. These dependencies are necessary to handle the worktrees created with the '/wt' command and to execute the cleanup process.