session

Inspects Git worktree-backed Claude sessions and reports sync state and drift from main.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill session-kord96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session
Source: https://github.com/Kord96/kordinate/tree/main/shared/skills/session
Command: npx skills add https://github.com/Kord96/kordinate --skill session-kord96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes inspection and non-destructive management of worktree-backed Claude sessions, making it easy to discover active sessions, verify Git sync and dirty state, and obtain exact next-step commands without mutating repository state.

Core Features & Use Cases

  • Enumerate session worktrees and report worktree path, branch, dirty/clean status, ahead/behind counts, and drift from main.
  • Show the current repository/worktree/branch and its sync state when inside a worktree.
  • Print exact claude-session commands to create new sessions, resume selected sessions, or inspect the current tree, and prune stale session metadata.
  • Use case: a developer coordinating parallel feature work across Git worktrees who needs a concise view of session state and the exact commands to resume or create Claude sessions.

Quick Start

Use the session skill to list active worktrees and their sync state by running session list.

Frequently Asked Questions about session

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

FAQPage Schema
How do I list active Git worktree sessions and check their sync status?

To inspect Git worktree sync state, the session skill runs a read-only git fetch --all --prune before reporting branch dirty status and ahead or behind counts, strictly avoiding any branch mutations or tmux state switching.

How do I resume a named Claude worktree session?

To resume a named Claude worktree session, use the session skill to print the exact claude-session resume commands for your selected worktree, allowing you to safely return to parallel feature work without mutating repository state.

Can I create new Claude worktree sessions without switching branches or tmux state?

Yes, you can create new Claude worktree sessions without switching branches or tmux state by having the session skill print the exact claude-session commands needed, ensuring non-destructive management of your parallel development workflow.

What is the best way to manage parallel Claude sessions across Git worktrees?

The best way to manage parallel Claude sessions is centralizing inspection with the session skill, which discovers active worktrees, verifies Git sync and dirty state, and prints exact next-step commands without mutating repository state.

How do I prune stale session metadata from Git worktrees?

To prune stale session metadata from Git worktrees, use the session skill to print the exact claude-session prune commands, clearing outdated worktree entries while maintaining a read-only evaluation of your current repository state.

Does the session skill modify my Git branches or switch tmux state during inspection?

No, the session skill does not modify Git branches or switch tmux state during inspection; it requires read-only evaluation with git fetch --all --prune, strictly reporting sync state and printing commands without mutating repository state.