wiki-session-ingestlisted

# wiki-session-ingest The other ingest skills (`wiki-ingest`, `wiki-import`) handle artifacts — URLs, files, pasted text. This one handles **the conversation itself**. When you debug an IPC reentrancy bug across two hours with Claude Code, the knowledge that compounds is the *reasoning trail* — what you tried, what didn't work, why you chose the fix you did. By the time you remember to write it down, half of it is gone. `wiki-session-ingest` reads the live session, asks you which knowledge points are worth keeping, and distills the selected ones through the existing `wiki-ingest` pipeline. ## When to use - After a deep debugging / design / refactor session that landed real conclusions (bug fix, decision, lesson, runbook step) - At the end of a multi-CLI day when knowledge is scattered across Claude Code + Codex CLI transcripts - Periodically as a sweep — "what did I figure out this week that isn't in the wiki?" Skip if: - The session was pure execution with no novel reasoning (e.g. mechanical refactor following an existing PRD) - You already wrote it down as an artifact and ingested it via `wiki-ingest` - The session was exploratory and never reached conclusions ## Pre-flight (orientation guard) Before the first phase, read the orientation files if not already done this session: ``` read_file {wiki_path}/SCHEMA.md # page types, tag taxonomy, policies read_file {wiki_path}/index.md # content catalog read_file {wiki_path}/log.md # last 20 lines