菜单
Synchronize the Obsidian vault (Meta-YGN/) with the current codebase state. Use after releases, major changes, or when vault docs may be stale.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | update-vault |
| description | Synchronize the Obsidian vault (Meta-YGN/) with the current codebase state. Use after releases, major changes, or when vault docs may be stale. |
| user-invocable | true |
| disable-model-invocation | false |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash, Agent |
Synchronize the Obsidian documentation vault at Meta-YGN/ with the current state of the Aletheia-Nexus codebase.
Read these sources of truth:
Cargo.toml — current versionCHANGELOG.md — latest changesREADME.md — what's confirmed vs experimental.claude-plugin/plugin.json — plugin versioncrates/*/src/ — actual module structurecrates/*/tests/ — test coveragegit log --oneline -20 — recent commitsRead Meta-YGN/00-Dashboard.md and compare:
For each vault file that is out of date:
Dashboard (00-Dashboard.md):
Architecture files (Architecture/*.md):
Features (Features/*.md):
Decisions (Decisions/*.md):
[[wikilinks]] resolve to existing filesupdated fields are set to todaygit add Meta-YGN/
git commit -m "docs(vault): sync Obsidian vault with codebase vX.Y.Z"
Templates/*.md) — only change if the template structure needs updatingReport:
Run a minimal metacognitive evaluation pass over the current task or repository change. Use to assess quality, calibration, and overhead.
Pressure-test the current plan or conclusion. Use when reasoning may be too linear, confidence seems too high, or there are plausible counter-hypotheses.
Compact the session into goal, verified facts, dead ends, open risks, and next actions. Use before long sessions, handoffs, context limits, or after repeated failed attempts.
Escalate when uncertainty is too high, risk exceeds agent capability, or human judgment is required. Use when verification fails, threats are found, or the agent is stuck.
Classify the task, identify risk, choose a strategy, and set a proof plan before non-trivial work. Use for architecture, migrations, auth, billing, concurrency, large refactors, or whenever failure would be costly.
Build a proof packet before finalizing work. Use for risky edits, architecture claims, dependency changes, security-sensitive work, and any answer that could mislead a reviewer.