pi-history-ingest
Ingest Pi coding agent session history into the Obsidian wiki. Use this skill when the user wants to mine their past Pi sessions for knowledge, import their ~/.pi/agent/sessions folder, extract insights from previous coding sessions, or says things like "process my Pi history", "add my Pi sessions to the wiki", "ingest ~/.pi", or "what have I worked on in Pi". Also triggers when the user mentions Pi sessions, Pi agent history, ~/.pi/agent/sessions, or Pi conversation logs.
Ar9av · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Ar9av/obsidian-wiki --skill pi-history-ingest技能说明
name: pi-history-ingest description: > Ingest Pi coding agent session history into the Obsidian wiki. Use this skill when the user wants to mine their past Pi sessions for knowledge, import their ~/.pi/agent/sessions folder, extract insights from previous coding sessions, or says things like "process my Pi history", "add my Pi sessions to the wiki", "ingest ~/.pi", or "what have I worked on in Pi". Also triggers when the user mentions Pi sessions, Pi agent history, ~/.pi/agent/sessions, or Pi conversation logs.
Pi History Ingest — Session Mining
You are extracting knowledge from the user's Pi coding agent sessions and distilling it into the Obsidian wiki. Pi sessions are stored as structured JSONL with a tree layout — your job is to follow the active branch, extract durable knowledge, and compile it.
Session knowledge closure: Pi session files are the only factual source for this skill. Do not add background knowledge from model training, other tools, package docs, local files, or the current conversation unless that fact appears in the selected session entries. If outside context seems useful, mark it as an open question or skip it — never present it as extracted session knowledge.
This skill can be invoked directly or via the wiki-history-ingest router (/wiki-history-ingest pi).
Before You Start
Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in llm-wiki/SKILL.md. Framework schema, provenance, safety, and operation-specific requirements take precedence.
WRITING.md preferences apply only to newly drafted or rewritten natural-language Markdown; preserve source content and structured records.
- Resolve config — follow the Config Resolution Protocol in
llm-wiki/SKILL.md(inline@nameoverride → walk up CWD for.env→ global config → prompt setup). This givesOBSIDIAN_VAULT_PATHandPI_HISTORY_PATH(defaults to~/.pi/agent/sessions) - Read
.manifest.jsonat the vault root to check what has already been ingested - Read
index.mdat the vault root to understand what the wiki already contains
Ingest Modes
Append Mode (default)
Check .manifest.json for each source file. Only process:
- Files not in the manifest (new sessions)
- Files whose modification time is newer than
ingested_atin the manifest
Use this mode for regular syncs.
Full Mode
Process everything regardless of manifest. Use after wiki-rebuild or if the user explicitly asks for a full re-ingest.
Pi Data Layout
Pi stores sessions under ~/.pi/agent/sessions/ (or the path set by PI_CODING_AGENT_SESSION_DIR).
~/.pi/agent/sessions/
├── --<cwd-path>--/ # Working directory with / replaced by -
│ └── <timestamp>_<uuid>.jsonl # Session JSONL file
└── ...
The session filename contains an ISO timestamp and UUID. The parent directory encodes the working directory where the session was created.
Session JSONL Format
Each .jsonl file is a sequence of JSON objects. The first line is always a session header; subsequent lines are tree entries with id and parentId.
Key entry types:
type | Purpose | Ingest? |
|---|---|---|
session | Header with cwd, version, id, timestamp | Metadata only |
message | Conversation turn (user, assistant, toolResult, bashExecution, etc.) | Primary source |
session_info | Display name set via /name | For session title |
compaction | Context compaction summary | High signal |
branch_summary | Summary when switching branches via /tree | High signal |
model_change | Model switch event | Skip |
thinking_level_change | Thinking level change | Skip |
custom | Extension state (not in LLM context) | Skip |
custom_message | Extension-injected message | Context only |
label | User bookmark/label | Skip |
Message roles inside message entries
user— user input;contentis string or(TextContent \| ImageContent)[]assistant— assistant response;contentis(TextContent \| ThinkingContent \| ToolCall)[]toolResult— tool execution result;contentis(TextContent \| ImageContent)[]bashExecution— bash command + output;command,output,exitCodebranchSummary— branch switch summary;summarystringcompactionSummary— compaction summary;summarystring
Key data sources ranked by value
messageentries (user+assistant) — full conversation transcripts; rich but noisycompactionentries — pre-synthesized summaries of older context; goldbranch_summaryentries — summaries of abandoned branches; good signalbashExecutionentries — concrete commands run; useful for workflow patternssession_infoentries — session name for topic inference
Skip model_change, thinking_level_change, custom (extension state), and label entries.
Step 1: Survey and Compute Delta
Scan PI_HISTORY_PATH and compare against .manifest.json:
# List all session files
find ~/.pi/agent/sessions -name "*.jsonl" -type f
# Or with custom path
find "$PI_HISTORY_PATH" -name "*.jsonl" -type f
Build an inventory. For each session file, record:
path— absolute pathcwd— decoded from parent directory name (--<path>--→/path)session_name— from the latestsession_infoentry (if any)modified_at— file mtimealready_ingested— presence in.manifest.json
Classify each file:
- New — not in manifest
- Modified — in manifest but file is newer than
ingested_at - Unchanged — already ingested and unchanged
Report a concise delta summary before deep parsing:
"Found N Pi sessions across K projects. Delta: X new, Y modified."
Step 2: Parse Session JSONL
For each selected session file, read it line by line. Because sessions use a tree structure, build the active branch first:
- Parse all entries int