agent-doc-discipline
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before…
LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)
$ npx -y skills add Yeachan-Heo/oh-my-claudecode --skill wiki --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/wikiContext preview
The summary Claude sees to decide when to auto-load this skill.
LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)
name: wiki description: LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model) triggers: ["wiki", "wiki this", "wiki add", "wiki lint", "wiki query"]
Persistent, self-maintained markdown knowledge base for project and session knowledge. Inspired by Karpathy's LLM Wiki concept.
Process knowledge into wiki pages. A single ingest can touch multiple pages.
wiki_ingest({ title: "Auth Architecture", content: "...", tags: ["auth", "architecture"], category: "architecture" })Search across all wiki pages by keywords and tags. Returns matching pages with snippets — YOU (the LLM) synthesize answers with citations from the results.
wiki_query({ query: "authentication", tags: ["auth"], category: "architecture" })Run health checks on the wiki. Detects orphan pages, stale content, broken cross-references, oversized pages, and structural contradictions.
wiki_lint()
Add a single page quickly (simpler than ingest).
wiki_add({ title: "Page Title", content: "...", tags: ["tag1"], category: "decision" })wiki_list() # Show all pages (reads index.md)
wiki_read({ page: "auth-architecture" }) # Read specific page
wiki_delete({ page: "outdated-page" }) # Delete a pageView wiki operation history by reading `.omc/wiki/log.md`.
Pages are organized by category: `architecture`, `decision`, `pattern`, `debugging`, `environment`, `session-log`
Use `[[page-name]]` wiki-link syntax to create cross-references between pages.
At session end, significant discoveries are automatically captured as session-log pages. Configure via `wiki.autoCapture` in `.omc-config.json` (default: enabled).
For Codex users: Check out oh-my-codex — the same orchestration experience for OpenAI Codex CLI. Liked OmC but found it a bit overkill? Try gajae-code.
Repo: Yeachan-Heo/oh-my-claudecode
Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before…
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then…
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly
Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior