Audit and clean stale Git worktrees with recovery SHA capture.
npx skills add https://github.com/mslshao/claude-harness --skill audit-worktrees
Please help me install this Agent Skill. Skill: audit-worktrees Source: https://github.com/mslshao/claude-harness/tree/main/dotclaude/skills/audit-worktrees Command: npx skills add https://github.com/mslshao/claude-harness --skill audit-worktrees
This Skill helps you audit and clean up stale Git worktrees created by agent, autopilot, and branch-based workflows without accidentally deleting active work. It reduces the manual effort of checking branch status, PR state, merge status, authorship, and recoverability before cleanup.
Ask the AI to audit worktrees in /workspaces/main and produce a deletion plan with verification evidence before removing anything.
High-intent search queries and answers about installing and using this skill.
Safely cleaning up stale Git worktrees requires auditing branch status, PR state, and merge status before deletion. This Skill automates that audit, classifies branches into delete or unshipped-work buckets, and captures recovery SHAs to prevent accidental deletion of active work.
Removing orphaned Git worktrees from autopilot or branch-based workflows requires evidence-based auditing. This Skill enumerates worktrees, checks dirty state, compares unique commits against main, and verifies PR resolution before generating a dependency-safe deletion plan.
Worktree cleanup prevents accidental deletion of unshipped work by capturing recovery SHAs and classifying branches. It checks for dirty states and unresolved pull requests, ensuring only merged-and-shipped or abandoned branches are pruned while active work remains untouched.
Yes, you can audit launch, autopilot, PR-intel, Jira-prefixed, chore, and fix worktree branches. The Skill applies specifically to worktrees under /workspaces/main, checking authorship classification and requiring verification evidence before producing a deletion plan.
Using multi-strategy PR lookup before deleting Git worktree branches ensures accurate merge verification and prevents data loss. This approach resolves pull request status through multiple search strategies, confirming whether branches are safely merged before pruning.
Automated Git worktree pruning should be avoided when branches contain uncommitted dirty states or unresolved pull requests. The Skill safeguards against this by applying confirmation gating and dependency-safe deletion order, ensuring active or unshipped work is not removed.
pcsensorCreate isolated Git worktrees to protect the current branch.
haryelramalhoDelete stale local git branches removed from the remote.
edlngAutomate development branch integration and cleanup after verifying test status.
Arist12Report git worktree status in a Markdown table with branch, dirty, and merged states.
