touch

Name: touch
Availability: InStock
Author: sanskarbasnet

Declare planned file edits to prevent merge conflicts during collaboration.

1|Updated May 4, 2026

Search Tags:#planning #collaboration #presence #scope #declare #structural-edit

Ready to run

npx skills add https://github.com/sanskarbasnet/fstack --skill touch

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Proactive scope declaration: broadcasts your intended edits to the brain to prevent collisions during collaborative coding.
Manual scope broadcast: allow you to declare scope for upcoming work without starting edits.
Automatic firing: triggers right before a structural edit to keep teammates informed.

Quick Start

Broadcast your intended edits using the /touch command with one or more file paths.

Frequently Asked Questions about touch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent merge conflicts during collaborative software development?▼

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.

How do I declare my editing scope before starting structural edits?▼

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.

What is proactive scope declaration in multi-file collaborative coding?▼

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.

Can I manually broadcast my intended scope without starting edits?▼

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.

When do I need to declare my editing scope for multi-file changes?▼

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.

Does collaborative coding require a heartbeat to publish planning presence?▼

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.