skills.rest
teslasoft-de
teslasoft-deCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

collab

Persist collaboration progress across Claude sessions using git branches.

1|1|Updated Jan 25, 2026
Search Tags:#git#collaboration#branching#handoff#context-switching#multisession
One-click install
npx skills add https://github.com/teslasoft-de/claude-skills-marketplace --skill collab-teslasoft-de
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: collab
Source: https://github.com/teslasoft-de/claude-skills-marketplace/tree/main/plugins/collab/skills/collab
Command: npx skills add https://github.com/teslasoft-de/claude-skills-marketplace --skill collab-teslasoft-de

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude conversations often get fragmented across sessions, making it hard to track progress, reuse context, and hand off work. This skill provides a Git-backed mechanism to persist collaboration state in feature branches, enabling seamless context switching between sessions.

Core Features & Use Cases

  • Multi-session tracking: Create and switch between collaboration branches to resume conversations.
  • Handoffs & publishing: Persist progress across teams and publish finalized work to master.
  • Vaults and code repos support: Works in both Obsidian vault-style projects and code repositories with consistent workflows.

Quick Start

Start a new collaboration by creating a branch for your project with /collab start.

Frequently Asked Questions about collab

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

FAQPage Schema
How do I persist Claude conversation context across multiple sessions?▼

You can persist Claude conversation context across multiple sessions by using git branches to track progress. This approach allows you to save, checkpoint, and resume multi-session work seamlessly.

What is the best way to hand off in-progress work to another Claude session?▼

The best way to hand off in-progress work is by saving collaboration state in a git feature branch. A new session can then resume the branch to restore full context and continue immediately.

Can I use git branching to manage context switching in Obsidian vaults?▼

Yes, you can use git branching to manage context switching in Obsidian vaults. The collaboration workflow supports both vault-style projects and code repositories with consistent branch operations.

How do I start a new collaboration branch for a Claude project?▼

To start a new collaboration branch for a Claude project, use the start command to create a dedicated feature branch. You can then save, checkpoint, and publish work to master when finalized.

Why does my Claude session lose context when switching between projects?▼

Claude sessions lose context when switching between projects because conversation state is fragmented. Using git branches to checkpoint and resume work provides a persistent mechanism to restore that context.

When should I abandon a collaboration branch instead of publishing it?▼

You should abandon a collaboration branch instead of publishing it when the work is no longer needed or the approach fails. Abandoning discards the branch state without merging incomplete changes into master.

Related Skills

Explore More Software Engineering Skills→
cbleckercblecker
5

rebasing-branch

Rebase a feature branch onto an updated base branch with conflict guidance.

Community
Basic
takemi-ohamatakemi-ohama

sync-main

Merge the latest default branch into the current working branch.

Community
Intermediate
onbjergonbjerg
4

jj

Provide jj version control command references and workflow guidance.

Community
Basic
koasis89koasis89

note

Create and manage notes using OMX persistent memory features.

Community
Basic