ingest-wiki

Files (1)

• SKILL.md

SKILL.md (first lines)

# ingest-wiki

Use this skill when you need a senior-engineer style mutation workflow:
explicit assumptions, minimal changes, and verification before completion.

## 1. Pick the mode

Choose the first matching mode:

- `ingest`
  - user says `ingest`
  - user asks to process `rawinput/`
  - user says they added a note, file, source, transcript, article, screenshot, or document to the wiki
- `lint`
  - user asks for a health check, lint, audit, consistency review, broken links check, or repo validation
- `save-output`
  - user asks to save the current answer, audit, report, architecture review, or analysis
- `direct-update`
  - any other explicit request to create, edit, move, merge, split, rename, reclassify, or repair wiki pages

Keep the existing skill name for compatibility.

## 2. Read sequence

Read in this order:

1. `WIKI_SCHEMA.md` if present
2. `AGENTS.md` and/or `CLAUDE.md`
3. `wiki/hot.md` if present
4. `wiki/overview.md`
5. `wiki/index.md`
6. recent entries from `wiki/log.md`
7. inspect `rawinput/` when the task is ingest, lint, or repo-health work

Transition behavior:

- if both `AGENTS.md` and `CLAUDE.md` exist, treat `CLAUDE.md` as canonical and `AGENTS.md` as compatibility routing
- if only one write-time contract exists, proceed with it
- if only `WIKI_SCHEMA.md` exists, allow read-only inspection and stop before mutating files
- if neither exists, stop and explain that the vault contract is missing

When reading `wiki/log.md`, read recent entries, not just the last physical lines.

## 2.1 Active memory retrieval

Treat `wiki/hot.md` as the cheap LLM memory gateway, not as a heavy wiki lookup.
Keep it under 500 words whenever you update it. It is a cache, not a journal.

Read `wiki/hot.md` first when the request touches the project, product, parser, design,
tech architecture, jobs, brand, wiki operations, or local workflow.

Use these query modes when the user asks a knowledge question or when you need context:

| Mode | Reads | Use when |
| --- | --- | --- |
| `quick` | `wiki/hot.md` and the retrieval map / top section of `wiki/index.md` | simple lookup, active context, or finding the owning page |
| `standard` | `wiki/hot.md`, `wiki/index.md`, and 1-3 targeted pages | normal product, tech, design, or wiki questions |
| `deep` | `wiki/hot.md`, `wiki/index.md`, recent `wiki/log.md`, and every relevant page | audits, synthesis, duplicate review, or migration planning |

If `wiki/hot.md` answers the question or points to the canonical page, do not broaden the read set.
If it is stale or missing, fall back to `wiki/overview.md` and `wiki/index.md`.
Never treat `wiki/hot.md` as canonical truth when it conflicts with a current durable page.

## 3. Mandatory preflight

Before any non-trivial write, state:

```text
Goal:
Assumptions:
Smallest safe change:
Verification:
```

Rules:

- if multiple interpretations exist, present them briefly instead of picking silently
- if a simpler approach exists, say so
- if uncertainty is material, ask or explicitly choose the safer interpretation
- do not continue with hidden confusion

## 4. Global rules

- never edit files under `raw/`
- ignore `rawinput/README.md`
- after every mutation, update `wiki/index.md`, `wiki/log.md`, and `wiki/hot.md`
- keep one active durable page per subject
- check for an existing page before creating a new one
- repair live references after any move, merge, split, or reclassification
- preserve historical log text unless it is meant to track the current active path
- keep pages compact, predictable, and easy to chunk
- use the category router and frontmatter contract in the write-time contract
- if the write-time contract is silent on a detail, fall back to `WIKI_SCHEMA.md`

Behavior constraints:

- do not overcomplicate the structure
- do not create speculative pages
- do not do drive-by cleanups
- every changed line should trace back to the request
- give a brief preview when useful, then proceed unless redirected

## 5. Ingest mode

### 5.1 Inspect staging

Scan `rawinput/`.
If there are no files other than `README.md`, stop and say that staging is empty.

### 5.2 Read and classify each file

For each staged file:

- read it fully
- identify the source type
- extract only the few facts that matter
- identify which durable pages should change
- detect contradictions or supersessions
- detect whether a new durable page is actually needed

From panamini/twoweeks-wiki, MIT.

More from panamini/twoweeks-wiki