Verified:GitHub

copilot-history-ingest

Distill GitHub Copilot CLI session history into structured Obsidian wiki pages.

4|Updated May 9, 2026

Search Tags:#checkpoints #obsidian #incremental sync #copilot cli #knowledge ingestion #wiki distillation #session-store db

Ready to run

npx skills add https://github.com/itsmarsss/memento --skill copilot-history-ingest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: copilot-history-ingest
Source: https://github.com/itsmarsss/memento/tree/main/obsidian-wiki/.cursor/skills/copilot-history-ingest
Command: npx skills add https://github.com/itsmarsss/memento --skill copilot-history-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of turning scattered GitHub Copilot CLI session logs into distilled, searchable Obsidian knowledge that reflects architecture decisions, debug notes, and reusable patterns.

Core Features & Use Cases

Incremental wiki ingestion (Append Mode): distills only new or updated sessions by comparing source state against the vault’s .manifest.json.
Full history rebuild (Full Mode): ingests everything regardless of manifest state, useful after a wiki-rebuild or when the user explicitly requests it.
Multi-source ingestion: mines Copilot CLI session directories, the global session-store.db (checkpoints, summaries, turns), and VS Code Copilot Chat transcripts to cluster knowledge into wiki pages.

Quick Start

Use this skill when you want to ingest your Copilot CLI history into your Obsidian vault by asking: ingest my copilot sessions into obsidian.

Frequently Asked Questions about copilot-history-ingest

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

FAQPage Schema

How do I convert GitHub Copilot CLI session history into Obsidian wiki pages?▼

To convert Copilot CLI session history into Obsidian wiki pages, this Skill scans Copilot storage paths and the session-store db, extracting checkpoints and turns while skipping internal reasoning fields to write structured vault pages.

What is incremental sync for Copilot session ingestion?▼

Incremental sync for Copilot session ingestion distills only new or updated sessions by comparing the source state against the vault's .manifest.json, appending delta changes rather than executing a full rebuild.

Can I ingest VS Code Copilot Chat transcripts into my Obsidian vault?▼

Yes, you can ingest VS Code Copilot Chat transcripts alongside Copilot CLI session directories and the global session-store db to cluster architecture decisions and debug notes into searchable wiki pages.

How do I do a full rebuild of Copilot session history in Obsidian?▼

A full rebuild of Copilot session history ingests everything regardless of the manifest state, recreating all wiki pages from scratch which is useful after a wiki-rebuild or when explicitly requesting complete data restoration.

Does the wiki ingestion process store internal reasoning fields from Copilot turns?▼

No, the wiki ingestion process explicitly skips internal reasoning fields when extracting checkpoint and turn content, ensuring only distilled, human-readable knowledge is written to the Obsidian vault pages.

What do I need to set up before ingesting Copilot sessions into Obsidian?▼

Before ingesting Copilot sessions, you need accessible Copilot CLI storage paths, an existing Obsidian vault, and a .manifest.json file to track state for computing deltas during the ingestion process.