Manage file ownership across sessions to prevent edit conflicts.
npx skills add https://github.com/wonder-zhang/openspec-autodev --skill claim-wonder-zhang
Please help me install this Agent Skill. Skill: claim Source: https://github.com/wonder-zhang/openspec-autodev/tree/main/skills/claim Command: npx skills add https://github.com/wonder-zhang/openspec-autodev --skill claim-wonder-zhang
In multi-session collaboration, multiple users can edit the same files at once, causing conflicts. This Skill provides a file-ownership mechanism to declare, release, and transfer ownership so only the owning session can modify matched files.
Run the claim add command to assign ownership of the files you are about to modify.
High-intent search queries and answers about installing and using this skill.
You prevent file edit conflicts by declaring file ownership so only the owning session can modify matched files. This mechanism coordinates sessions to avoid concurrent edits on the same file patterns.
You claim ownership of specific file patterns by running the add action with your desired patterns. This assigns the matched files to your session, preventing other sessions from editing them concurrently until you release or transfer ownership.
Yes, you can coordinate file ownership across remote machines by optionally using a coordination server. This server handles cross-machine collaboration and conflict resolution for file ownership transfers between local and remote sessions.
The best way to transfer file ownership between sessions is using the transfer action. This moves the ownership of specific file patterns from one session to another, allowing the new session to safely modify the files without conflicts.
No, you do not need a coordination server to manage file ownership locally. The coordination server is optional and is only required when you need to sync file ownership and resolve conflicts across remote machines in cross-machine collaboration.
ceshineDefine and package agent Skills with SKILL.md frontmatter and resource directories.
tranhieuttRemove the .freeze lock file to re-enable merges after release freezes.
AlabamaMikeAnalyze git history to identify coordination bottlenecks in codebases.
vrcmsStandardize Git branching, commit conventions, and merge workflows.
