Adds llm-wiki to the Workflows and Innovations section. It is a Logseq-based implementation of Andrej Karpathy's LLM Wiki gist — Claude Code maintains the graph for you (ingest sources, query, lint, status), with schema-driven consistency and a two-layer cache architecture.
Why it fits
The "Workflows and Innovations" section already lists tools that automate parts of Logseq maintenance (Lupin, logseq-doctor, Logseq Advanced Query Builder, etc.). llm-wiki extends this idea further: it lets an LLM maintain the entire knowledge graph — extracting facts from new sources, updating cross-references, enforcing the schema, and running health checks (orphans, stale pages, broken refs, credential leaks).
The Logseq outliner format is what makes the LLM use case work — every block is independently addressable, so an ingest can append new content without disrupting existing structure. This is genuinely Logseq-native; the same pattern is much harder in flat-markdown systems.
Project details
License: MIT
Status: Active (~65★, last commit ~1 week ago)
Tech stack: Claude Code + Logseq (Obsidian also supported, but Logseq is the recommended/primary target)
Standalone: No Logseq plugin, no Logseq HTTP API dependency — operates directly on the markdown files
Test plan
Entry follows the section's existing one-line format ("by Author - Description")
Repo URL resolves and is publicly accessible
Description honestly reflects the project (no hype)
Section choice (Workflows and Innovations) matches existing similar entries
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/logseq/awesome-logseq/pull/75
**Author:** [@MehmetGoekce](https://github.com/MehmetGoekce)
**Created:** 4/26/2026
**Status:** ✅ Merged
**Merged:** 4/27/2026
**Merged by:** [@logseq-cldwalker](https://github.com/logseq-cldwalker)
**Base:** `master` ← **Head:** `add-llm-wiki`
---
### 📝 Commits (1)
- [`177f563`](https://github.com/logseq/awesome-logseq/commit/177f5633c7bfa057df15f09d5e70921838a0a308) Add llm-wiki to Workflows and Innovations
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
## Summary
Adds [llm-wiki](https://github.com/MehmetGoekce/llm-wiki) to the **Workflows and Innovations** section. It is a Logseq-based implementation of [Andrej Karpathy's LLM Wiki gist](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) — Claude Code maintains the graph for you (ingest sources, query, lint, status), with schema-driven consistency and a two-layer cache architecture.
## Why it fits
The "Workflows and Innovations" section already lists tools that automate parts of Logseq maintenance (Lupin, logseq-doctor, Logseq Advanced Query Builder, etc.). llm-wiki extends this idea further: it lets an LLM **maintain the entire knowledge graph** — extracting facts from new sources, updating cross-references, enforcing the schema, and running health checks (orphans, stale pages, broken refs, credential leaks).
The Logseq outliner format is what makes the LLM use case work — every block is independently addressable, so an ingest can append new content without disrupting existing structure. This is genuinely Logseq-native; the same pattern is much harder in flat-markdown systems.
## Project details
- **License:** MIT
- **Status:** Active (~65★, last commit ~1 week ago)
- **Tech stack:** Claude Code + Logseq (Obsidian also supported, but Logseq is the recommended/primary target)
- **Standalone:** No Logseq plugin, no Logseq HTTP API dependency — operates directly on the markdown files
## Test plan
- [x] Entry follows the section's existing one-line format ("by Author - Description")
- [x] Repo URL resolves and is publicly accessible
- [x] Description honestly reflects the project (no hype)
- [x] Section choice (Workflows and Innovations) matches existing similar entries
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/logseq/awesome-logseq/pull/75
Author: @MehmetGoekce
Created: 4/26/2026
Status: ✅ Merged
Merged: 4/27/2026
Merged by: @logseq-cldwalker
Base:
master← Head:add-llm-wiki📝 Commits (1)
177f563Add llm-wiki to Workflows and Innovations📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
Summary
Adds llm-wiki to the Workflows and Innovations section. It is a Logseq-based implementation of Andrej Karpathy's LLM Wiki gist — Claude Code maintains the graph for you (ingest sources, query, lint, status), with schema-driven consistency and a two-layer cache architecture.
Why it fits
The "Workflows and Innovations" section already lists tools that automate parts of Logseq maintenance (Lupin, logseq-doctor, Logseq Advanced Query Builder, etc.). llm-wiki extends this idea further: it lets an LLM maintain the entire knowledge graph — extracting facts from new sources, updating cross-references, enforcing the schema, and running health checks (orphans, stale pages, broken refs, credential leaks).
The Logseq outliner format is what makes the LLM use case work — every block is independently addressable, so an ingest can append new content without disrupting existing structure. This is genuinely Logseq-native; the same pattern is much harder in flat-markdown systems.
Project details
Test plan
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.