llm-wiki
Purpose
Keeps a persistent, Git-backed Markdown wiki under docs/wiki that grows with the project instead of rediscovering facts on every question.
Source Skill purpose
When to use it
Use llm-wiki when a project needs a persistent Git-backed knowledge base instead of repeatedly rediscovering the same decisions and evidence. It ingests sourced material into separate source, entity, concept, decision and lesson pages linked to each other. It answers questions from the wiki and checks sources, contradictions, duplicate titles, broken links and orphan pages. A lint report describes what it finds without silently repairing the knowledge base. The skill also serves the knowledge step of a proofline run.
Sources remain repository files, while disposable run folders provide history rather than authority. Contradicted pages keep both claims visible and outdated pages move to an archive. Ordinary repository edits are not logged as wiki operations.
Source Skill purpose
How it works
The skill definition states no numbered steps.
Source Skill definition
Key rules
- Keep raw session summaries immutable after ingestion, so their original evidence remains available.
Source Hard rules
- Attach repository-file sources to important claims; disposable run identifiers are history rather than sources.
Source Hard rules
- Mark contradictions explicitly and retain both claims instead of silently deleting one.
Source Hard rules
- Archive outdated pages rather than deleting them from the knowledge base.
Source Hard rules
- Let explicit task requirements and current code take precedence over wiki knowledge.
Source Hard rules
Output and gate
Output
The skill definition states no output.
Source Skill definition
Gate
- This knowledge skill records no gate and makes no product-code change.
Source Gate rule
Source
Source Skill definition