Back to Skills

copilot-history-ingest

Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages. Use this skill when the user wants to capture their Copilot CLI sessions into a personal wiki — extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages. Triggers on phrases like "ingest my copilot sessions into obsidian", "add my copilot history to my wiki", "pull my copilot session history into the vault", "capture what I've learned from copilot into obsidian", "just

3,221stars322forksUpdated 8/17/2026

Security Assessment

Safe(92/100)
Security Score92/100

About copilot-history-ingest

Copilot-history-ingest captures a user's past GitHub Copilot CLI session history and distills it into an Obsidian wiki as searchable knowledge pages — extracting architecture decisions, debug notes, and reusable patterns from conversations that are rich but messy. It solves the problem of valuable engineering context being locked inside ephemeral Copilot sessions by mining that history and compiling the signal into a personal knowledge base.

The skill resolves configuration (vault path and Copilot history locations) through a defined protocol, then reads a manifest and index to know what already exists. It supports an append mode (default) that only processes new or updated sessions using timestamps, and a full mode that reprocesses everything. It scans three Copilot data locations: the per-session `session-state` directories (workspace metadata, event logs, checkpoints, session summaries), the global `session-store.db` SQLite database (the highest-value, pre-summarized cross-session record with sessions, turns, checkpoints, file references, and a full-text search index), and VS Code workspace storage transcripts. A detailed reference documents each event type and, importantly, an extraction strategy that deliberately skips encrypted/opaque and internal reasoning fields, using only visible content and structured checkpoint summaries.

It targets individual developers who use Copilot CLI and maintain an Obsidian vault and want an automated, incremental way to turn their session history into durable notes. Behaviorally it reads local session data (including SQLite databases and JSONL logs) and writes markdown into a local vault — no network exfiltration — and it is conscious about not surfacing encrypted internal reasoning.

FAQ

What does this skill do?

It reads your GitHub Copilot CLI session history and distills it into distilled, searchable knowledge pages inside an Obsidian wiki, capturing architecture decisions, debug notes, and patterns.

Which data does it read?

Three local sources: per-session `~/.copilot/session-state` directories, the global `~/.copilot/session-store.db` SQLite database, and VS Code Copilot-chat workspace-storage transcripts.

Does it re-ingest everything each time?

No. Append mode (the default) uses a manifest and updated-at timestamps to process only new or changed sessions; full mode reprocesses everything, typically after a rebuild or on explicit request.

What does it need configured?

An Obsidian vault path plus Copilot history paths, resolved via a config protocol (inline override, a walked-up .env, or a config file); the VS Code storage path is platform-specific and may need to be supplied.

Is any sensitive data excluded?

Yes. The extraction strategy explicitly skips encrypted/opaque reasoning and internal reasoning-text fields, using only visible message content and structured checkpoint summaries; output is written locally to your vault with no external transmission.

All Files

2 files
references/copilot-data-format.md12.0 KB
View
SKILL.md17.3 KB
View

Install copilot-history-ingest

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill