git-worktree-decisionDecide 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.
Install via ClawdBot CLI:
clawdbot install clarezoe/git-worktree-decisionGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Sep 29, 2026
A developer is mid-way through a long-running feature branch with a dirty index, warm build cache, and an attached debugger. A P1 production bug arrives that must ship immediately without losing the current working state or committing half-finished code.
An engineering team launches multiple autonomous coding agents to work on separate tickets in the same repo. Without separate worktrees, agents overwrite each other's uncommitted edits and each agent's test suite observes the other's half-written files.
A platform team needs to diff the output of a legacy version against a refactored version at the same moment, or port a fix across two major release lines. Both working states must be live and runnable simultaneously to compare behavior.
A developer has reproduced a hard-to-catch bug and has a bisect or debugger session running that must not be disturbed. Meanwhile, routine feature work still needs to proceed on the same repository without invalidating the reproduction.
After weeks of ad-hoc parallel work, a team finds several half-set-up worktrees holding branches that cannot be deleted and whose purpose no one remembers. They need a decision framework to determine which worktrees should never have existed and to enforce teardown discipline.
A platform or developer-experience team codifies worktree decision rules into onboarding guides, linters, and pre-commit hooks to reduce branch collisions and abandoned checkouts across the organization. The value shows up as fewer lost hours debugging flaky parallel test runs.
A product that spins up isolated worktrees per agent session, parameterizes external singletons like ports and databases, and tears down environments automatically. Customers pay per concurrent agent or per managed workspace.
Paid courses, workshops, and newsletter content teaching engineering judgment around git workflows, worktree concurrency, and agent-safe branching. Monetized through course sales, sponsorships, or team training contracts.
💬 Integration Tip
Wire this decision into pre-worktree automation so the concurrency and singleton checks fire before `git worktree add`, and pair it with a teardown reminder or cleanup job. For agent platforms, parameterize ports, databases, and compose projects per worktree before launching parallel sessions.
Scored Sep 29, 2026
通过网页抓取获取 GitHub 按日/周/月增长的热门仓库。当用户询问 GitHub 趋势、热门项目、本周热点或「什么在 GitHub 上 trending」时使用。可输出列表或 JSON,无需 API Key。
GitHub 操作技能 - 创建仓库、推送代码、管理 Release。全自动,无需用户干预。
Deep-dive analysis of GitHub projects. Use when the user mentions a GitHub repo/project name and wants to understand it — triggered by phrases like "帮我看看这个项目...
Git-based version control for OpenClaw system configuration changes. Provides two core capabilities: (1) SAVE - Create a checkpoint before sensitive operatio...
Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers.
PR Review Expert