
indexion-identity
Detect and review name/content drift in code using indexion identity audit, then plan verified renames, moves, folder changes, or splits.
- Installs
- 4.9K
- Last 24h
- —
- Trending rank
- —
- Security
- Pass
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/trkbt10/indexion-skills --skill indexion-identity- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads indexion-identity automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
-
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 verify
-
Verify before editing:
indexion doc graph --format=text <path> indexion grep --semantic=name:<symbol> . rg "<name-or-term>" <path> -
Choose the smallest confirmed operation:
- Treat
insufficient-contentas 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.
- Treat
-
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.
FAQ
What does the indexion-identity skill do?
Detect and review name/content drift in code using indexion identity audit, then plan verified renames, moves, folder changes, or splits.
How do I install indexion-identity?
Run npx skills add https://github.com/trkbt10/indexion-skills --skill indexion-identity in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/indexion-identity/ (personal) or .claude/skills/indexion-identity/ (project).
Which AI agents can use indexion-identity?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is indexion-identity safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains indexion-identity?
It is published by trkbt10 in trkbt10/indexion-skills. It has 4,915 recorded installs.
More from trkbt10/indexion-skills
indexion-readme
trkbt10/indexion-skills
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.
indexion-sdd
trkbt10/indexion-skills
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.
indexion-documentation
trkbt10/indexion-skills
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?"
indexion-refactor
trkbt10/indexion-skills
After writing code, detect and clean up duplication at three levels — copy-paste blocks, cross-package shared code, unnecessary wrappers, and concept-level SoT violations. Detect with indexion, fix, and verify.
indexion-wiki
trkbt10/indexion-skills
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.
indexion-segment
trkbt10/indexion-skills
Split text into contextual chunks for RAG/embedding pipelines. Document segmentation and section extraction using window, tfidf, punctuation, or hybrid strategies chosen by intent.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.