skills.rest
thesobercoder
thesobercoderCOMMUNITY
Explore all skills by this author →
Website𝕏@thesobercoderGitHub

session-dump

Export Claude Code and opencode sessions as per-session markdown transcripts.

Updated Aug 23, 2026
Search Tags:#git#documentation#claude-code#opencode#transcripts#session-dump
One-click install
npx skills add https://github.com/thesobercoder/skills --skill session-dump
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-dump
Source: https://github.com/thesobercoder/skills/tree/main/session-dump
Command: npx skills add https://github.com/thesobercoder/skills --skill session-dump

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Long-running design conversations live inside private agent storages and drift when contexts reset. This skill exports those conversations from Claude Code and opencode into committed, per-session markdown transcripts in a repository's .sessions directory, ensuring a durable, reviewable record that survives tool switching and rate limits.

Core Features & Use Cases

  • Exports per-session transcripts as separate <session-id>.md files
  • Supports Claude Code and opencode sources, no hidden state, and deterministic output
  • Ideal for PRD grilling, design sprints, and handoff documentation across team tools

Quick Start

Run the bundled dump scripts from inside your target repo to generate per-session markdown transcripts under .sessions/.

Frequently Asked Questions about session-dump

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

FAQPage Schema
How do I save Claude Code planning chats as durable transcripts?▼

To save Claude Code planning chats as durable transcripts, run the bundled dump scripts inside your target repository. This exports conversations as per-session markdown files into a .sessions directory, preventing data loss during context resets.

What is the best way to preserve multi-session design conversations across tool switches?▼

Preserving multi-session design conversations across tool switches requires exporting them to git-tracked markdown transcripts. This skill deterministically archives discourse from Claude Code and opencode into a committed .sessions directory for reviewable records.

Can I export opencode session histories to markdown files?▼

Yes, you can export opencode session histories to markdown files. The dump scripts support both opencode and Claude Code sources, creating separate deterministic markdown files per session ID without hidden state.

Do I need external dependencies to generate git-tracked session transcripts?▼

No, you do not need external dependencies to generate git-tracked session transcripts. The scripts rely solely on the Python standard library and the bundled scripts within the repository to export per-session markdown archives.

Why does my agent planning context drift during long-running design sprints?▼

Agent planning context drifts during long-running design sprints because private agent storages reset contexts over time or hit rate limits. Exporting these conversations to committed markdown transcripts ensures a durable record that survives.

Related Skills

Explore More Content & Communication Skills→
xlelibertyxleliberty

merge

Merge successful agent branches into a base repository and archive failures with git tags.

Community
Advanced
Largo2z9Largo2z9
1

export-session

Export Claude Code sessions into structured markdown transcripts for archiving.

Community
Intermediate
AMindToThinkAMindToThink
4

archive-logs

Archive Claude Code conversation logs into project-local JSONL and Markdown records.

Community
Advanced
deomiarndeomiarn
5

website-builder

Generate a Markdown sitemap with page structure and pnpm commands.

Community
Advanced