git-worktree-decision
33 score
Decide whether a piece of work deserves its own git worktree, before creating one. Use when about to start work that would disturb a dirty or warm working tree, when an urgent fix interrupts work in progress, when launching concurrent/parallel agent sessions on one repo, when tempted to `git stash` or `git switch` to make room, or when worktrees have accumulated and you need to know which should never have existed. Covers the concurrency test, the shared-external-state blocker that makes worktrees backfire, and the teardown commitment. Not a worktree how-to: mechanics, per-worktree ports, and dependency symlinking are out of scope.
Ranked #99 out of 177 indexed skills.
Is this your tool? Claim this listing to add maintainer context, get a verified badge, and unlock analytics.
Claim listing → Signal Breakdown
Installs 0
Freshness GitHub not linked
Issue Health GitHub not linked
Stars GitHub not linked
Platform Breadth 1 platform
Contributors GitHub not linked
Description Detailed
How to Improve
Platforms medium impact
Badge
[](https://agentrank-ai.com/skill/clawhub-git-worktree-decision/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge) <a href="https://agentrank-ai.com/skill/clawhub-git-worktree-decision/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge"><img src="https://agentrank-ai.com/api/badge/skill/clawhub-git-worktree-decision" alt="AgentRank"></a>