claude-history-ingest
Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.
Ar9av · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Ar9av/obsidian-wiki --skill claude-history-ingest技能说明
name: claude-history-ingest description: > Ingest Claude Code conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Claude conversations for knowledge, import their ~/.claude folder, extract insights from previous coding sessions, or says things like "process my Claude history", "add my conversations to the wiki", "what have I discussed with Claude before". Also triggers when the user mentions their .claude folder, Claude projects, session data, past conversation logs, local-agent-mode sessions, or audit logs.
Claude History Ingest — Conversation Mining
You are extracting knowledge from the user's past Claude Code conversations and distilling it into the Obsidian wiki. Conversations are rich but messy — your job is to find the signal and compile it.
This skill can be invoked directly or via the wiki-history-ingest router (/wiki-history-ingest claude).
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_PATHandCLAUDE_HISTORY_PATH(defaults to~/.claude) - Read
.manifest.jsonat the vault root to check what's already been ingested - Read
index.mdat the vault root to know what the wiki already contains - Project Scoping — read
WIKI_SKIP_PROJECTSfrom config (comma-separated substrings). Exclude any project directory whose name contains one of them from every step below (scan, delta, sampling, manifest writes). If the user names extra projects to skip this run, add them. Apply the exclusion once, uniformly — don't hand-writegrep -vfilters into individual commands, which drifts between the scan and manifest steps.
Ingest Modes
Append Mode (default)
Check .manifest.json for each source file (conversation JSONL, memory file). Only process:
- Files not in the manifest (new conversations, new memory files, new projects)
- Files whose modification time is newer than their
ingested_atin the manifest
This is usually what you want — the user ran a few new sessions and wants to capture the delta.
Canonical paths when comparing. The manifest keys are absolute paths with
~expanded (seellm-wiki/SKILL.md→.manifest.json). Before deciding a file is "new", expand its path the same way — otherwise a file already tracked as~/.claude/...looks new when you scanned it as/Users/me/.claude/...(or vice-versa) and gets re-ingested. Thescripts/manifest.pyhelper does this for you:# New/modified sources, honoring WIKI_SKIP_PROJECTS + --skip, paths already canonical: python3 "$OBSIDIAN_WIKI_REPO/scripts/manifest.py" delta "$OBSIDIAN_VAULT_PATH" \ --scan "$CLAUDE_HISTORY_PATH/projects/*/memory/*.md" # One-time repair if the manifest already mixes ~ and absolute keys: python3 "$OBSIDIAN_WIKI_REPO/scripts/manifest.py" normalize "$OBSIDIAN_VAULT_PATH" --dry-runThe helper is optional — if it's unavailable, do the same expansion inline before every manifest lookup and write.
Pre-extraction (recommended — run before ingest)
Raw JSONL files are 80-90% noise: tool_use blocks, thinking blocks, progress events, and
file-history-snapshot entries dominate by byte count. The scripts/extract-jsonl.py helper
strips all of that and writes compact signal-only JSON to ~/.claude/extracted/, achieving
50–200× file-size reduction (e.g. 12 MB JSONL → 64 KB extracted). This lets the skill read
5–10× more conversations per run within the same token budget.
Run it as a pre-step before invoking this skill:
# First run — extract everything (skip excluded projects)
python3 "$OBSIDIAN_WIKI_REPO/scripts/extract-jsonl.py" --skip tsg,autom8
# Incremental — only sessions modified in the last day
python3 "$OBSIDIAN_WIKI_REPO/scripts/extract-jsonl.py" \
--since "$(date -v-1d +%Y-%m-%d)" --skip tsg,autom8
Extracted files live at ~/.claude/extracted/<project-dir>/<session-id>.json and contain:
{
"session_id": "uuid",
"project": "-Users-name-myapp",
"cwd": "/Users/name/myapp",
"start_ts": "...",
"end_ts": "...",
"n_turns": 18,
"n_user_words": 620,
"turns": [
{"role": "user", "text": "..."},
{"role": "assistant", "text": "..."}
]
}
When Step 3 reads conversations, always prefer the extracted file over the raw JSONL. (See Step 3.)
If extract-jsonl.py was not run first, fall back to raw JSONL — but note the coverage will be
shallower because each raw file costs far more tokens to read.
Conversation Sampling Heuristic
A history path can hold hundreds of conversation JSONLs — do not try to read them all. Per project:
- If the project already has memory files (
memory/*.md), ingest those first (they are pre-distilled signal), then also process conversations not yet in the manifest — new conversations should still be captured even for memory-rich projects. - If the project has no memory files, read only the 3 most recent conversations (by mtime) to characterize it. Prefer pre-extracted files (see above) — they are cheap enough that you can read 5–10 in the same token budget as 1 raw JSONL.
- Always report what you sampled vs skipped (e.g. "agenttower: 7 memory files + 4 new conversations ingested, 14 unchanged conversations skipped"), so the coverage gap is visible rather than silent.
Full Mode
Process everything regardless of manifest. Use after a wiki-rebuild or if the user explicitly asks.