Indexion Identity
Run Indexion identity audits to spot function, file, and folder names that no longer match what the code actually does, then verify before renames or splits.
Install
npx skills add https://github.com/trkbt10/indexion-skills --skill indexion-identityWhat is this skill?
- Runs `indexion identity audit` for mechanical scans with optional JSON report output to `.indexion/cache/identity/report
- Treats each audit row as a review candidate with name, expected_summary, actual_summary, assessment, and recommendation
- Distinguishes actual drift, overbroad content, and insufficient content before any rename or split
- 3-step pipeline: scan → compare summaries → verify with `indexion doc graph`, semantic grep, and ripgrep
- Scopes naming to files, folders, and graph-level declarations—not every local variable as an independent target
Adoption & trust: 505 installs on skills.sh; 1 GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Improve Codebase Architecturemattpocock/skills
Zoom Outmattpocock/skills
Caveman Reviewjuliusbrussee/caveman
Requesting Code Reviewobra/superpowers
Receiving Code Reviewobra/superpowers
Request Refactor Planmattpocock/skills
Journey fit
Primary fit
Identity drift is a pre-change quality gate: you review naming against graph-derived summaries before shipping refactors or approving structural edits. The workflow is review-first—mechanical scan, compare expected vs actual summaries, then verify with doc graph and search—not a greenfield build task.
Common Questions / FAQ
Is Indexion Identity safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Indexion Identity
# Identity Audit Workflow 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. ## Pipeline 1. Run the mechanical scan: ```bash indexion identity audit . ``` For a machine-readable queue: ```bash indexion identity audit --format=json --output=.indexion/cache/identity/report.json . ``` 2. Treat each row as a review candidate, not proof. Compare: - `name`: the scoped name inferred by the identity package - `expected_summary`: what the path/name/scope predicts - `actual_summary`: graph-derived declarations, docs, module notes, and path terms - `assessment`: whether this is actual drift, overbroad content, or insufficient content - `recommendation`: first operation to verify 3. Verify before editing: ```bash indexion doc graph --format=text <path> indexion grep --semantic=name:<symbol> . rg "<name-or-term>" <path> ``` 4. Choose the smallest confirmed operation: - Treat `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. - Rename a symbol when its implementation is cohesive but the name is stale. - Rename a file when its declarations are cohesive but the file name is stale. - Rename a folder when contained files share a clearer parent concept. - Move a file when it fits an existing folder better than its current one. - Split a file when candidates show multiple dominant responsibilities. 5. After changes: ```bash 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.