Declare planned file edits to prevent merge conflicts during collaboration.
npx skills add https://github.com/sanskarbasnet/fstack --skill touch
Please help me install this Agent Skill. Skill: touch Source: https://github.com/sanskarbasnet/fstack/tree/main/touch Command: npx skills add https://github.com/sanskarbasnet/fstack --skill touch
This skill helps you preemptively declare which files you plan to edit, updating your presence with a planning status and an active_files list so other agents surface your intended scope before the first edit occurs.
Broadcast your intended edits using the /touch command with one or more file paths.
High-intent search queries and answers about installing and using this skill.
To prevent merge conflicts, you can declare your planned editing scope to broadcast your active files. This publishes a planning presence to teammates before any structural edits occur.
You declare your editing scope by broadcasting intended file paths using the /touch command. This manually updates your presence status and active_files list before you begin making changes.
Proactive scope declaration is the process of broadcasting intended edits to a shared presence system. It allows other agents to surface your active files and prevents collisions before the first edit occurs.
Yes, you can manually broadcast your intended scope for upcoming work without starting edits. This feature allows you to declare planned file changes and update your planning presence ahead of time.
You need to declare your editing scope whenever you plan structural edits across multiple files. The declaration triggers automatically right before an edit to keep teammates informed of your active files.
Publishing a planning presence requires the fstack-brain heartbeat. It uses this mechanism to broadcast your active_files list and planning status, ensuring teammates are aware of your intended scope.
sanskarbasnetRun fstack-brain sync to display live agent status, intents, handoffs, and recent decisions.
bejranondaValidate Claude Code plugin manifests and directory structures for compliance.
akiyoshiBlock Edit and Write operations outside a chosen directory.
CuriousLearnerAnalyze Git merge conflict types and propose automated or manual resolution strategies.
