coordinate-worktrees-and-threads
/coordinate-worktrees-and-threads
Assign worktree, branch, write, validation, integration, and cleanup ownership before parallel repository work. Use when a worker will inspect or modify repository state outside the coordinator's worktree.
- Author
- gaelic-ghost ↗
- Repository
- socket ↗
- Licence
- Apache-2.0
- Last repository change
- 26.08.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Assign worktree, branch, write, validation, integration, and cleanup ownership before parallel repository work. Use when a worker will inspect or modify repository state outside the coordinator's worktree.
Original author description
Assign worktree, branch, write, validation, integration, and cleanup ownership before parallel repository work. Use when a worker will inspect or modify repository state outside the coordinator's worktree.
How it works
- Launch Record
- Rules
- Completion
SKILL.md preview
--- name: coordinate-worktrees-and-threads description: Assign worktree, branch, write, validation, integration, and cleanup ownership before parallel repository work. Use when a worker will inspect or modify repository state outside the coordinator's worktree. --- # Coordinate Worktrees And Threads Establish repository ownership before a worker begins. A thread is not a worktree, and a branch is not permission to make shared Git mutations. ## Launch Record For every worker, record the worker/task identity, coordinator, repository and base commit, worktree path, branch, read/write scope, allowed Git operations, validation lane, output/merge target, final report route, and retention or cleanup decision. ## Rules - Give parallel writers disjoint files or directories and separate worktrees. - When a Codex-managed worktree versus a plain Git worktree is itself a decision, hand that host-specific choice to `repository-skills:codex-gui-worktree-workflow`; retain this skill's host-neutral ownership record in either case. - Serialize Git operations that change shared repository state. A worker must not assume it owns tags, merges, release branches, deletion, or cleanup. - Serialize heavy build and test lanes unless the environment explicitly proves they are independent and safe. - Keep final integration, conflict resolution, release, branch accounting, and cleanup with the coordinator unless the user explicitly assigns them. - When a worker returns, report branch/worktree state, commits, validation, uncommitted changes, artifacts, and the recommended integration action. ## Completion The coordinator explicitly chooses whether to retain the worker thread or worktree for follow-up, merge/preserve its result, archive it, or remove it after branch accounting. Never delete a worktree or branch merely because a worker says it is done.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named coordinate-worktrees-and-threads.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 6f13f1ae22ab (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100git-worktree
Use when work needs an isolated git worktree, such as parallel feature branches, reviewing a PR without disturbing the current checkout, or cleaning up old worktrees. - 100worktree-list
Read-only inventory of active worktrees: branch, status, sync state, staleness. Use when user asks what worktrees exist, "list worktrees", "show my worktrees", "what's in flight", "which branches have worktrees", "stale worktrees", "any forgotten worktrees", or wants a… - 90worktrees:finish
Use when completing work in a worktree. Handles PR creation or direct merge, worktree removal, and branch cleanup. Invoke with "/worktrees:finish" or when user mentions "finish worktree", "clean up worktree", "merge worktree", "done with worktree", or "complete worktree work". - 86coordinate
Run several coding agents on one repository as a coordinator, each worker in its own git worktree with a plan-first session prompt. Use when the user wants to plan sessions, launch and watch workers, review plans, check CI and merge their PRs one at a time. Opt-in. - 90worktrees-plan-recipe
Worktrees — Plan, follow or revise how this repository makes git worktrees, one per change. Use when the person wants changes done in worktrees ("trabaja en un worktree", "un worktree por desarrollo", "work in a worktree"), when a session says the worktrees feature has no recipe… - 90git-worktree-manager
Manage parallel development with Git worktrees: creation with port allocation, environment sync, branch isolation, and cleanup. Use when working multiple branches at once, running parallel CI validations, or isolating agent workspaces.