菜单
Detect and review name/content drift in code using `indexion identity audit`, then plan verified renames, moves, folder changes, or splits.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
README construction — initialize template structure, generate per-package READMEs from doc comments, plan writing tasks, assemble root README from docs/ and package READMEs via doc.json config, and verify edits with `plan drift`.
Generate and use a pre-edit structure brief so coding agents learn likely owners, consumer surfaces, and unsafe edit locations before implementing.
Generate SDD requirements from RFCs/specs and quantitatively verify implementation conformance. spec draft → spec align → spec verify → automated validation loop with codex/claude. Operate spec-to-impl drift gates as CI checks.
Documentation analysis — assess coverage, detect code-to-doc drift with plan reconcile, visualize dependencies with doc graph. Answers "what needs docs?" and "are docs still accurate?"
Project wiki lifecycle — create pages, track source changes with ingest, update stale pages, lint structural integrity, detect code-to-doc drift with reconcile, and manage search indexes. A runbook for navigating and maintaining the wiki as an agent.
Debug and inspect KGF specs — view tokenization results, parse trees, and extracted edges from source files. Use when adding/fixing language support or when indexion's analysis output looks wrong.
| name | indexion-identity |
| description | Detect and review name/content drift in code using `indexion identity audit`, then plan verified renames, moves, folder changes, or splits. |
Use this skill when checking whether function, file, or folder names still match their contents.
The CLI scans files, folders, and graph-level declaration symbols. It does not treat every local variable, parameter, or field as an independent naming target; those can still influence the containing file summary. File names are evaluated with parent scope, and declaration-heavy files should normally be read as evidence-thin until follow-up inspection proves an actual rename or split.
Run the mechanical scan:
indexion identity audit .
For a machine-readable queue:
indexion identity audit --format=json --output=.indexion/cache/identity/report.json .
Treat each row as a review candidate, not proof. Compare:
name: the scoped name inferred by the identity packageexpected_summary: what the path/name/scope predictsactual_summary: graph-derived declarations, docs, module notes, and path termsassessment: whether this is actual drift, overbroad content, or insufficient contentrecommendation: first operation to verifyVerify before editing:
indexion doc graph --format=text <path>
indexion grep --semantic=name:<symbol> .
rg "<name-or-term>" <path>
Choose the smallest confirmed operation:
insufficient-content as an evidence problem, not a naming-drift proof.
Inspect whether the file is intentionally declarative/thin, unsupported by the
graph extractor, empty, or missing doc/declaration material before renaming.After changes:
moon info && moon fmt
moon test
indexion identity audit .
The audit is designed to surface review work. Do not maximize the score mechanically; verify the actual code ownership and references first.