copilot-history-ingest

Extract Copilot CLI session histories into Obsidian wiki pages.

Updated Feb 2, 2016
One-click install
npx skills add https://github.com/zjykzk/blog --skill copilot-history-ingest-zjykzk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilot-history-ingest
Source: https://github.com/zjykzk/blog/tree/main/.agents/skills/copilot-history-ingest
Command: npx skills add https://github.com/zjykzk/blog --skill copilot-history-ingest-zjykzk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest GitHub Copilot CLI conversation history and distill it into Obsidian pages to capture architecture decisions, debugging notes, and patterns for future reference.

Core Features & Use Cases

  • Ingest per-session histories from Copilot data sources (session-state, session-store.db, and VS Code transcripts) and convert them into topic-driven wiki pages.
  • Provide high-signal knowledge via distilled checkpoints and session summaries, enabling quick discovery and reuse.
  • Map sessions to projects by cwd/repository to generate project-level concepts and skills within the vault.

Quick Start

Run the Copilot history ingest workflow to convert your Copilot CLI sessions into Obsidian pages.

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 history into Obsidian wiki pages?

This Skill distills GitHub Copilot CLI conversation history into Obsidian wiki pages by extracting per-session data from session-state, session-store.db, and VS Code transcripts. It generates topic-driven pages capturing architecture decisions and debugging notes.

What is the best way to map Copilot CLI sessions to specific projects in a knowledge base?

Mapping Copilot CLI sessions to projects is handled by analyzing the cwd/repository from the session histories. The Skill uses this repository data to generate project-level concepts and skills within your Obsidian vault automatically.

Does Copilot history ingest process VS Code transcripts and session-store databases safely?

Yes, Copilot history ingest processes VS Code transcripts and session-store.db safely by respecting privacy and security constraints. It omits sensitive data and processes checkpoints before turns to ensure secure knowledge extraction.

Can I extract architecture decisions and debugging notes from Copilot CLI conversations automatically?

Yes, you can extract architecture decisions and debugging notes from Copilot CLI conversations automatically. The Skill distills CLI histories into high-signal knowledge pages, providing session summaries and checkpoints for quick discovery and reuse.

How do I run the Copilot history ingest workflow to build topic-driven pages?

To run the Copilot history ingest workflow, execute the provided workflow to convert your Copilot CLI sessions into Obsidian pages. It processes session histories and outputs distilled, topic-driven wiki pages across your projects.

What are the limitations of ingesting Copilot CLI history into a wiki?

Limitations of ingesting Copilot CLI history include the omission of sensitive data to respect privacy constraints. Processing is restricted to per-session histories from Copilot data locations, filtering out restricted content before generating wiki pages.