ush-concurrent-edit-coordination

What problem does it solve? When two agents or workstreams edit code at the same time, teams often guess at collision risk from plans, titles, or open PRs and either over-coordinate or miss real conflicts. This Skill determines whether two in-flight changes actually overlap on the same checkout, file hunks, or public contract before any coordination happens. ## Core Features & Use Cases - Evidence-based entry gate: Only proceeds when real diff evidence (git status, git diff --name-only, git diff --cached --name-only) shows both workstreams actively editing implementation source; otherwise it skips rather than guessing. - Overlap classification: Categorizes collisions as none, shared-checkout, hunk, contract, or duplicate, and assigns an owner and dependent workstream when overlap exists. - Read-only safety contract: Never modifies another workstream's checkout, branch, staged changes, or commits, and never re-engages finished work. - Use Case: Two AI coding sessions are editing the same API contract; run this Skill to check collision risk and decide whether one merge must wait for the other. ## Quick Start Ask the agent to check whether the two currently active workstreams editing this repository actually collide on the same files or public contract before merging.