Communitygithub.com

wiki

LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)

wiki とは?

wiki is a Claude Code agent skill that lLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model).

対応Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/wiki

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

ドキュメント

wiki は何をしますか?

Persistent, self-maintained markdown knowledge base for project and session knowledge. Inspired by Karpathy's LLM Wiki concept.

Operations

Ingest

Process knowledge into wiki pages. A single ingest can touch multiple pages.

wiki_ingest({ title: "Auth Architecture", content: "...", tags: ["auth", "architecture"], category: "architecture" })

Query

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" })

Lint

Run health checks on the wiki. Detects orphan pages, stale content, broken cross-references, oversized pages, and structural contradictions.

wiki_lint()

Quick Add

Add a single page quickly (simpler than ingest).

wiki_add({ title: "Page Title", content: "...", tags: ["tag1"], category: "decision" })

List / Read / Delete

wiki_list()           # Show all pages (reads index.md)
wiki_read({ page: "auth-architecture" })  # Read specific page
wiki_delete({ page: "outdated-page" })    # Delete a page

Log

View wiki operation history by reading .omc/wiki/log.md.

Categories

Pages are organized by category: architecture, decision, pattern, debugging, environment, session-log

Storage

  • Pages: .omc/wiki/*.md (markdown with YAML frontmatter)
  • Index: .omc/wiki/index.md (auto-maintained catalog)
  • Log: .omc/wiki/log.md (append-only operation chronicle)

Cross-References

Use [[page-name]] wiki-link syntax to create cross-references between pages.

Auto-Capture

At session end, significant discoveries are automatically captured as session-log pages. Configure via wiki.autoCapture in .omc-config.json (default: enabled).

Hard Constraints

  • NO vector embeddings — query uses keyword + tag matching only
  • Wiki pages are git-ignored by default (.omc/wiki/ is project-local)

Model Routing

  • haiku — quick lookups, lightweight inspection, narrow docs work
  • sonnet — standard implementation, debugging, and review
  • opus — architecture, deep analysis, consensus planning, and high-risk review
  • fable — Claude Fable 5 (above Opus); pass it explicitly on the Task call or pin it per agent with agents.<name>.model
  • The session model chosen with /model applies to the main loop only. Delegated agents run on their pinned tier unless the Task call passes model explicitly or the agent is overridden via agents.<name>.model. To run delegated work on Fable, use one of those two surfaces; selecting Fable in /model alone does not change delegation.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

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 reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 sediment pass; opt-in for any other agent-facing doc edit. The companion of minimal-code-discipline: that one disciplines code, this one disciplines papers.

ai-slop-cleaner

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

ask

Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly

ask-navigator

Shipyard

autopilot

Full autonomous execution from idea to working code

autoresearch

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

cancel

Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state

configure-notifications

Configure notification integrations (Telegram, Discord, Slack) via natural language

debug

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

deepinit

Deep codebase initialization with hierarchical AGENTS.md documentation

deep-interview

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

drydock

Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.

execute

Carry an approved task through to working, verified code

external-context

Invoke parallel document-specialist agents for external web searches and documentation lookup

graph

Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery

harbor

Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence. Agent-autonomous for facts and for actions covered by standing authorization; signed for every new judgment. Never merges.

hud

Configure HUD display options (layout, presets, display elements)

launch

Shipyard

loft

Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks. Use when a design question stalls in words, when a navigator map carries a loft ticket, or when a spec discussion reaches

minimal-code-discipline

YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

関連スキル