Claude Code Plugins

Community-maintained marketplace

Feedback

collab-start

@leaf76/session-collab-mcp
2
0

Initialize session collaboration for multi-session conflict prevention. Use this at the start of a conversation or when you need to register a new collaboration session.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name collab-start
description Initialize session collaboration for multi-session conflict prevention. Use this at the start of a conversation or when you need to register a new collaboration session.
allowed-tools mcp__session-collab__*

Session Collaboration Startup

Initialize session collaboration to prevent conflicts when multiple Claude Code sessions work on the same codebase.

Required Actions

Execute these steps in order:

Step 1: Start Session

Call mcp__session-collab__collab_session_start with:

  • project_root: Current working directory
  • name: A descriptive name based on the task (e.g., "feature-auth", "bugfix-api")

Important: Store the session_id from the response - you need it for all subsequent calls.

Step 2: Review Active Sessions

Check the response for:

  • Number of active sessions
  • Other session names and their last activity time
  • memory_hint: Whether other sessions have working memories

If other sessions are active, inform the user about potential collaboration.

Step 3: Check Existing Claims

Call mcp__session-collab__collab_claims_list with:

  • status: "active"
  • project_root: Current working directory

If there are active claims:

  • List which files/symbols are claimed
  • Show which session holds each claim
  • Display the stated intent

Step 4: Load Working Memory (Recommended)

Call mcp__session-collab__collab_memory_active with:

  • session_id: Your session ID
  • priority_threshold: 70 (default, gets pinned + high priority memories)

This retrieves important context from previous work:

  • Findings: Discovered facts, root causes
  • Decisions: Architectural choices made
  • State: Current status, files being worked on
  • Important: Critical information that must not be lost

Display any relevant memories to establish context continuity.

Step 5: Configure Mode (Optional)

If needed, call mcp__session-collab__collab_config with:

  • session_id: Your session ID
  • mode: One of:
    • "strict": Always ask user before proceeding with conflicts
    • "smart" (default): Auto-proceed with safe content, ask for blocked
    • "bypass": Warn only, don't block

Output Format

Provide a summary in the user's language:

Session Collaboration Initialized

Item Value
Session ID xxx-xxx-xxx
Session Name your-session-name
Project Path /path/to/project
Active Sessions N
Active Claims M
Working Memories K

Other Active Sessions (if any)

  • session-name-1 (last active: X minutes ago)
  • session-name-2 (last active: Y minutes ago)

Active Claims (if any)

  • file.ts - claimed by other-session for "intent description"

Previous Context (if any memories found)

Display relevant findings, decisions, or important notes from working memory.

Reminders

  • Always call collab_check before editing files
  • Use collab_claim to reserve files before modification
  • Use collab_memory_save to persist important findings/decisions
  • Call collab_release when done with files
  • Call collab_session_end when conversation ends