Knowledge Wiki Summary

Knowledge Wiki Summary

Batch process all stale or new knowledge base files and write their wiki summaries. Incremental — only processes files whose content has changed since the last summary was written.

Steps

1. Establish the working directory

The knowledge base root is the Git repository root. Run git rev-parse --show-toplevel and store the result as KNOWLEDGE_PATH.

Use KNOWLEDGE_PATH for all subsequent steps.

2. Find files that need summarizing

Run:

node {KNOWLEDGE_PATH}/scripts/wiki/wiki-summary.mjs list-stale

Output format:

{ "sources": ["Posts/Buy Me a Coffee.md", ...] }

Each entry is a source file path relative to KNOWLEDGE_PATH.

If sources is empty, print Nothing to summarize. and stop.

3. Process each file

For each entry in sources, run the following sub-steps in order.

3a. Read the source file

If the source file is 1500 lines or fewer, read it directly with the Read tool in the main context and proceed to step 3b.

If the source file is over 1500 lines, spawn a subagent to read the full source. Brief the subagent with:

• The source file path: {KNOWLEDGE_PATH}/{source_path}
• The full step 3b content-generation instructions (copy the entire section into the prompt)

Instruct the subagent to:

1. Read the full source file using the Read tool, using offset/limit for subsequent pages if the file is truncated
2. Generate and return all of the following (do not write any files):
   • Tags (3–8 lowercase English tags, comma-separated)
   • Title (in source language)
   • ## Summary content (2–4 sentences in source language)
   • ## Key Concepts bullets (in source language)
   • ## Notable Details content (in source language)
   • A one-line English description of the source document (used in step 3d)

When the subagent returns, skip the generation part of step 3b and proceed directly to the create command in step 3c, using the content the subagent returned.

3b. Generate the summary content

Language: Write the title, summary prose, and key points in the same language as the source document. If the source is in Mandarin, write in Mandarin. If in Cantonese, write in Cantonese. Only fall back to English if the source language is ambiguous or mixed. Section headers (## Summary, ## Key Concepts) stay in English regardless of source language. When writing in English, use American English spelling (e.g. "realize" not "realise", "organize" not "organise").

Generate the following content from the source document:

1. tags — 3–8 lowercase English tags based on content, comma-separated

2. Title — infer from content or filename, in source language

3. ## Summary — 2–4 sentences in source language summarizing the document's main subject, argument, or purpose

4. ## Key Concepts — a bulleted list of 3–8 key concepts this source covers, each formatted as:

   - [[Wiki/Concepts/{concept-slug}|{Display Name}]] — {brief description in source language}

   • Concept slugs are always lowercase English kebab-case regardless of source language.
   • Display Name is the correctly-cased human-readable title always in English, regardless of source language (e.g. [[Wiki/Concepts/restful-api|RESTful API]]). Infer the English concept name from the source text — don't derive it mechanically from the slug.
   • Concept files may not exist yet — broken links are acceptable here.

5. ## Notable Details — any specific facts, figures, quotes, findings, or techniques worth preserving verbatim, in source language