Agent skill
refactor-lexical-ontology
Audit identifiers and namespaces for lexical-semantic and ontological correctness. Detect semantic role misalignment (agent/tool/process/artifact), derivational misuse (e.g., -er agent nouns), and category errors between modules, packages, classes, functions, and data artifacts. Output a single Markdown report with actionable fixes.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/lexical-ontology
Metadata
Additional technical details for this skill
- author
- Jordan Godau
- keywords
-
naming ontology lexical semantic agent process artifact suffix convention
- references
-
[ "01_INTENT.md", "02_PRECONDITONS.md", "03_RULES.md", "04_PROCEDURE.md", "05_OUTPUT.md" ]
SKILL.md
Instructions
Read all references in references/ before using this skill.
Signals
- The user says: "naming feels off", "planner vs planning", "module naming convention", "agentive suffix misuse", "semantic role mismatch", "ontology drift", "lexical audit"
- A naming refactor is planned or ongoing
- Confusion exists between thing vs doer vs process vs tool in identifiers
- The codebase has inconsistent conventions between directories/modules/classes/functions
References
Directory: references/
01_INTENT.md02_PRECONDITIONS.md03_RULES.md04_PROCEDURE.md05_OUTPUT.md
Scripts
If scripts are present, also read scripts/INDEX.md and follow any automated steps first.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?