alive:session-context-rebuild

Merge multiple sessions into a single walnut context and detect conflicts.

124|7|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/alivecontext/alive --skill alive-session-context-rebuild
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alive:session-context-rebuild
Source: https://github.com/alivecontext/alive/tree/main/plugins/alive/skills/session-context-rebuild
Command: npx skills add https://github.com/alivecontext/alive --skill alive-session-context-rebuild

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merges multiple sessions into a single working context and detects conflicts between parallel sessions, enabling seamless resumption of work.

Core Features & Use Cases

  • Orchestrates a phased reconstruction (Scout, Deep Read, Merge & Present, Resume) to rebuild context from session histories and touched files.
  • Detects and surfaces conflicts across sessions, and produces a merged working state with unresolved decisions flagged for human review.

Quick Start

Use this skill to merge multiple sessions into one coherent context and resume work with conflicts identified.

Frequently Asked Questions about alive:session-context-rebuild

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

FAQPage Schema
How do I merge multiple agent sessions into a single coherent context?

To merge multiple agent sessions into a single coherent context, this skill orchestrates a phased reconstruction using subagents to read session histories, detect conflicts, and rebuild the working state for seamless resumption.

What is the best way to resolve conflicts between parallel sessions touching the same files?

Resolving conflicts between parallel sessions requires detecting changes across touched files; this skill uses a swarm of subagents during the merge phase to surface conflicts and flag unresolved decisions for human review.

How does context reconstruction work when resuming work after days away?

Context reconstruction works by executing a phased approach—Scout, Deep Read, Merge & Present, and Resume—where subagents read files and session histories to rebuild the working state and identify any conflicts.

Does merging walnut session contexts require any external dependencies?

Merging walnut session contexts requires no external dependencies, relying entirely on its internal phased approach and swarm of subagents to read files and reconstruct the working state.

When do I need to use a multi-session context merge?

You need a multi-session context merge when resuming work after days away or when parallel sessions have touched the same walnut, requiring conflict detection and reconstruction of a single coherent working state.

Why are unresolved decisions flagged during the context merge process?

Unresolved decisions are flagged during the context merge process because parallel sessions may introduce conflicting changes to the same files, requiring human review to determine the correct final working state.