菜单
Use when existing autology docs/ nodes need syncing or updating — when a doc is out of date after a code change, after refactors, when triage identifies existing nodes to verify, or for periodic full audits. Not for new items (use capture) or knowledge questions (use explore).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when user is new to Autology, asks "how does Autology work", wants to learn about knowledge capture, or requests a guided introduction.
Use after significant project actions — commit, push, PR — or when the team settles on how to build or operate the system: a technology choice, a process, a rule, or a standard. Running close to the action keeps captured knowledge more accurate and complete.
Use to permanently record a project decision, convention, pattern, or known issue into the knowledge base (docs/) — triggers on explicit save intent ("remember this", "save this", "document this"), decision or convention announcements ("we decided", "settled on", "the rule is"), or triage output classifying new items to capture. Distinct from conversational memory — this writes to docs/.
Use whenever the user asks about this project's decisions, architecture, conventions, or how something works in this codebase — do NOT answer from general knowledge, always look it up in docs/. Trigger on questions like "why did we choose X?", "how does Y work here?", "what's our convention for Z?", "what docs reference X?", or any question about this project's specific choices. Also use for explicit /autology:explore-knowledge commands (overview, neighborhood, path). Searches docs/, follows wikilinks, and synthesizes grounded answers from the knowledge base.
Use after significant actions (commits, decisions, refactors) or when asked to triage changes — classifies knowledge items as existing or new and provides topology hints for sync and capture.
| name | sync-knowledge |
| description | Use when existing autology docs/ nodes need syncing or updating — when a doc is out of date after a code change, after refactors, when triage identifies existing nodes to verify, or for periodic full audits. Not for new items (use capture) or knowledge questions (use explore). |
docs/ nodes must accurately reflect the actual codebase and decisions. This skill verifies that and fixes any discrepancies in-place.
Two modes:
Precondition: if triage has not run this session, run /autology:triage-knowledge first, then fast sync. Full mode is only used when the user explicitly passes full.
/autology:sync-knowledge # fast — verifies nodes triage identified
/autology:sync-knowledge full # full audit — no triage needed
Precondition: triage has already run and returned matched existing nodes.
Use triage's matched nodes as the sync scope:
Existing nodes from triage (→ sync):
- docs/foo.md — matches [item description]
Connected: [[bar]], [[baz]] | Tags: arch, api
Also include any connected nodes listed in the topology hints.
For each matched doc:
## Sync Report (fast)
**Changed files checked**: N
**Docs matched**: N
**Docs updated**: N
### Updated
- docs/example.md — updated function count (3 → 4)
### No changes needed
- docs/other.md — still accurate
If no docs reference any changed file: "No docs reference the changed files — nothing to sync."
Glob: docs/*.md
Read: each file (frontmatter + content)
Extract: title, type, tags, content, wikilinks ([[target]] patterns)
Identify the project's key files based on its structure:
Glob: common project manifests (package.json, go.mod, Cargo.toml, pyproject.toml, etc.)
Glob: source directories identified from project structure
Read: key config files (hooks/, scripts/, config/, etc.)
Code → No Doc: Significant components exist but no node documents them
Doc → No Code: Nodes describe things that no longer exist
Doc ≠ Code: Nodes exist and code exists but they disagree
Extract all [[target]] patterns from node content.
For each target, check if docs/{target}.md exists.
Report broken wikilinks.
[[B]] link → suggest linkFix policy: For Doc ≠ Code discrepancies — edit the doc in-place immediately, then report what was fixed. For Code → No Doc gaps — report only (capture handles new nodes).
## Sync Report (full)
### Code → No Doc
- **[Component Name]**: what/where → fix: capture as [type] with tags [...]
### Doc → No Code / Doc ≠ Code
- **[Node Title]**: claim vs reality → fix: edit or delete
### Broken Wikilinks
| Source | Broken Link |
|--------|-------------|
### Missing Wikilinks
| Node A | Node B | Reason |
|--------|--------|--------|
**Summary**: N gaps, N broken links, N missing links
| Mistake | Fix |
|---|---|
| Running fast mode without triage output | Run /autology:triage-knowledge first automatically — triage output is what fast mode syncs against. |
| Falling back to full mode when triage is missing | Full mode is only for explicit full argument. Default path: run triage → fast sync. |
| Report findings without fixing | Edit docs in-place immediately when discrepancies are found. |
| Judge doc accuracy without reading code | Always Read the actual file before comparing. |
| Run full audit on every action | Fast mode (post-triage) for daily use; full mode for periodic audits. |