菜单
Audit and maintain the vault-backed llm-wiki knowledge base, including stale pages, low-confidence or contested captures, superseded captures, missing frontmatter, and broken wikilinks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use as the canonical first-stage Agmo workflow when the user wants idea exploration, design tradeoffs, or requirement shaping before planning or implementation.
Run a Codex-native structured code review using agmo-critic and agmo-verifier where evidence is needed.
Harvest `debt:` markers across the repo into a read-only ledger without modifying code.
Use when prior notes, durable project knowledge, or vault-backed context should influence the current task.
Use when one execution lane is no longer enough and work should escalate to the durable `agmo team ...` runtime.
Use when the user wants a GitHub issue created from the current conversation or repo context. Triggers on requests like "이슈 만들어", "깃허브 이슈", "create issue", or "new issue". If the source artifact is an existing vault note, use `note-to-issue` instead.
| name | wiki-maintain |
| description | Audit and maintain the vault-backed llm-wiki knowledge base, including stale pages, low-confidence or contested captures, superseded captures, missing frontmatter, and broken wikilinks. |
| argument-hint | [project name] |
Use this when session-start reports wiki health warnings, when wiki context looks stale, or before relying on full llm-wiki context for a project.
Run:
agmo wiki maintain --project <project> --format markdown
For machine-readable output:
agmo wiki maintain --project <project> --format json
Working rules:
<vault_root>/.agmo/llm-wiki as the SSOT for startup knowledge.agmo wiki context --project <project> --full only when full body context is needed.LOW_CONFIDENCE and CONTESTED findings before using the affected page as evidence.agmo wiki migrate-wisdom --scope project --project <project> --dry-run to preview migration from legacy .agmo/memory/wisdom.json.