alive:session-context-rebuild SKILL.md skillA
alive:session-context-rebuild from alivecontext/alive is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alivecontext/alive/alive:session-context-rebuild@git:20260511.5023f6dPins git:20260511.5023f6d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alivecontext/alive
- Path
plugins/alive/skills/session-context-rebuild/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260511.5023f6d, committed May 11, 2026
- First version recorded
- Apr 20, 2026
- Size
- 6,901 bytes
- Repository stars
- 131
- License
- MIT
Merge multiple sessions into one working context and detect conflicts between parallel sessions. Dispatches subagent swarm to read files touched, extract log history, and resolve contradictory state. Use when resuming after days away or when parallel sessions may have written conflicting decisions. For browsing or reviving individual sessions, use alive:session-history instead.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Session Context Rebuild You're returning to work that spans multiple sessions — possibly conflicting ones. The context window is empty but the walnut isn't. This skill dispatches subagents to deeply reconstruct what happened, what changed, where conflicts exist, and what the merged state should be. Then you resume with full context as if you never left. --- ## When to Use - Returning to a walnut after days/weeks away - Context was lost to compaction mid-session - Multiple sessions touched the same walnut in parallel and need merging - Picking up someone else's work in a shared walnut - "What was I doing here?" moments --- ## Process ### Phase 1: Scout (single agent) Dispatch one `general-purpose` subagent to map the territory. It reads the `session-history/SKILL.md` file and applies its browse logic against `.alive/_squirrels/`, then reports back: - Which sessions touched this walnut, when, by whom (engine) - Which files each session worked on (`working:` field in squirrel YAML) - Which bundles were active - Whether sessions overlap (parallel/conflicting work) - Unsaved stash items from crashed sessions …
Read the whole file at its exact version.
How to install
mdr add alivecontext/alive/alive:session-context-rebuild@sha256:9df1f94275fb5e80The line at the top of this page pins the label git:20260511.5023f6d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fo4ywkfivcrpp5o4)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 20, 2026 and May 11, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260511.5023f6d latest | 2026-05-11 | 5023f6d | 6,901 B | A | view · diff |
| git:20260420.407e0c4 | 2026-04-20 | 407e0c4 | 6,863 B | A | view · diff |
| git:20260420.4b94201 | 2026-04-20 | 4b94201 | 6,292 B | A | view · diff |
| git:20260420.9ec5551 | 2026-04-20 | 9ec5551 | 6,363 B | A | view · diff |
| git:20260420.c1cdbd6 | 2026-04-20 | c1cdbd6 | 6,231 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6901 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
alivecontext/alive · 131 stars · license MIT · pushed 2026-10-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fo4ywkfivcrpp5o4 GET https://markdownregistry.com/api/v1/resolve?ref=alivecontext/alive/alive:session-context-rebuild GET https://markdownregistry.com/api/v1/blob/9df1f94275fb5e801a2d2f2b1bc4c3e3b48acf9b53a58f7d57b201c7221767c5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.