skills.rest
pax-k
pax-kCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

copilot-history-ingest

Extract Copilot CLI session history into Obsidian wiki pages with frontmatter and provenance.

6|2|Updated May 11, 2026
Search Tags:#checkpoints#obsidian#sessions#wiki#transcripts#copilot#ingest
One-click install
npx skills add https://github.com/pax-k/war-gov-uap-wiki --skill copilot-history-ingest-pax-k
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: copilot-history-ingest
Source: https://github.com/pax-k/war-gov-uap-wiki/tree/main/.cursor/skills/copilot-history-ingest
Command: npx skills add https://github.com/pax-k/war-gov-uap-wiki --skill copilot-history-ingest-pax-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages, enabling you to capture architecture decisions, debugging notes, and patterns from Copilot conversations into searchable, source-grounded wiki content.

Core Features & Use Cases

  • Distills Copilot sessions into structured wiki pages that preserve insights and decisions.
  • Captures debugging notes, design patterns, and architecture decisions for future reference.
  • Use cases include onboarding teammates, documenting recurring patterns, and building a knowledge base from Copilot transcripts.

Quick Start

Instruct the system to ingest your Copilot CLI session history into your Obsidian vault to generate knowledge 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 Copilot CLI session history into Obsidian wiki pages?▼

To convert Copilot CLI session history into Obsidian wiki pages, this skill ingests conversations, decisions, and patterns from session transcripts and maps them to project pages and global concepts with frontmatter and provenance.

Can I extract architecture decisions from VS Code Copilot transcripts into a searchable wiki?▼

Yes, you can extract architecture decisions from VS Code Copilot transcripts. The ingestion process distills session history into structured knowledge pages that capture debugging notes, design patterns, and decisions for future reference.

What is the best way to document Copilot CLI sessions for team onboarding?▼

The best way to document Copilot CLI sessions for team onboarding is to distill historical transcripts into structured knowledge pages. This captures recurring patterns and architecture decisions into searchable, source-grounded wiki content.

Does the ingestion process for Copilot sessions include internal reasoning content?▼

No, the ingestion process for Copilot sessions explicitly excludes internal reasoning content. It focuses solely on extracting conversations, decisions, and patterns to produce concise wiki pages with updated manifests.

What data sources are supported for ingesting Copilot session history into a wiki?▼

Supported data sources for ingesting Copilot session history into a wiki include session-store.db, per-session checkpoints, and VS Code copilot transcripts, which are all mapped to project pages and global concepts.

Related Skills

Explore More Software Engineering Skills→
zjykzkzjykzk

copilot-history-ingest

Extract Copilot CLI session histories into Obsidian wiki pages.

Community
Advanced
huidgehuidge
2

llm-wiki

Ingest diverse sources into a layered Markdown wiki with cross-links and provenance markers.

Community
Advanced
WesleyMFrederickWesleyMFrederick

writing-requirements-documents

Generate Obsidian requirements documents with block anchors and validated wiki links.

Community
Advanced
Nero-kkNero-kk

data-ingest

Convert unstructured text sources into distilled Obsidian wiki pages.

Community
Advanced