Help us improve
Share bugs, ideas, or general feedback.
From autology
Traverses docs/ knowledge graph via search and wikilinks to answer project questions on decisions, architecture, conventions. Supports /autology:explore-knowledge overview, neighborhood, path.
npx claudepluginhub curt-park/autology --plugin autologyHow this skill is triggered — by the user, by Claude, or both
Slash command
/autology:explore-knowledgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Answer user questions about the project by traversing the autology knowledge graph.
Auto-generates AGENTS.md from knowledge graph topology. Never stale because computed, not authored. Use after refactoring or on schedule.
Builds a local knowledge graph of code, docs, and mixed media using tree-sitter extraction and LLM-based relationship inference. Query via CLI commands instead of reading raw files.
Generates and updates README.md and API reference docs by building a knowledge graph of your codebase with graphify, then writing accurate docs from it.
Share bugs, ideas, or general feedback.
Answer user questions about the project by traversing the autology knowledge graph. Search docs/ for relevant nodes, follow wikilinks to build context, and return rich answers grounded in documented decisions, conventions, and architecture.
Use explore instead of reading a doc directly when: the user asks a question (rather than requesting a specific doc), or when the topic may span multiple connected nodes.
When the user asks a question about the project (conventions, architecture, decisions, rationale):
docs/ for keywords from the questionThe <node> argument is a title-slug — the filename without the .md extension (e.g., redis-storage-decision for docs/redis-storage-decision.md).
/autology:explore-knowledge overview)Process:
docs/*.md, read each file's frontmatter and wikilinksOutput:
/autology:explore-knowledge <node>)Process:
[[slug]]docs/ for [[target-slug]] to find nodes that reference the targetOutput: node title, type, tags, and connections for each hop
/autology:explore-knowledge path A B)Process:
Output: A → [intermediate] → B with each hop labeled
/autology:explore-knowledge overview # graph overview
/autology:explore-knowledge <node> # neighborhood (2-hop BFS)
/autology:explore-knowledge path A B # shortest path
| Mistake | Fix |
|---|---|
| Answer from memory instead of docs | Always Read the actual doc nodes before answering |
| Stop at 1-hop neighbors | Follow wikilinks to 2-hop for richer context |
| Ignore node type and tags | Include type/tags in answers — they add classification context |
| Only follow outgoing links in neighborhood | Also grep docs/ for [[node-name]] to find nodes that link TO the target |
| Speculate when question has false premise | State what IS documented; never construct a rationale not found in docs |