From claude-mneme
Look up what Mneme knows about a file, function, or entity. Use when the user asks "what do you know about X", wants to check entity history, or asks about file/function activity and mentions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-mneme:entityThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user wants to query what Mneme knows about a specific entity (file, function, error, or package). They may have provided the entity name after the command.
The user wants to query what Mneme knows about a specific entity (file, function, error, or package). They may have provided the entity name after the command.
If the user provided a query (e.g., /entity auth.ts), search for it directly.
If no query was provided, ask the user: "What entity would you like to look up? (e.g., a file name, function, or package)"
Use the mem-entity script to search the entity index:
node "${CLAUDE_PLUGIN_ROOT}/scripts/mem-entity.mjs" [options] [query]
Options:
--list - List all indexed entities with their mention counts--category <cat> - Filter by category: files, functions, errors, packages<query> - Search for entities matching this name (partial match supported)# Look up a specific file
node "${CLAUDE_PLUGIN_ROOT}/scripts/mem-entity.mjs" auth.ts
# List all indexed files
node "${CLAUDE_PLUGIN_ROOT}/scripts/mem-entity.mjs" --list --category files
# Search for functions containing "handle"
node "${CLAUDE_PLUGIN_ROOT}/scripts/mem-entity.mjs" --category functions handle
The script returns JSON with:
matches - Entities matching the queryname, category, mentions, lastSeen, contexts (recent activity)For /entity auth.ts:
auth.ts (file) — 12 mentions, last seen 2 hours ago
Recent activity:
- [commit] Added JWT validation to auth middleware
- [task] Implementing auth flow
- [prompt] User asked about auth token refresh
npx claudepluginhub edimuj/claude-mneme --plugin claude-mnemeNavigates large codebases via MCP server: symbol search, reference/caller lookups, commit history, blame, diffs, and code outlines without reading source files.
Unified context retrieval via context_research. Searches PRs, docs, messaging platforms, issue trackers, and code history to surface WHY code works the way it does, what was tried before, and what constraints apply. TRIGGER when: you need decision history, prior art, or conventions before modifying code; planning, scoping, or researching a topic; investigating a bug or incident; you need filtered lookups across issues, messages, or PRs (e.g., "open bugs in PROJECT", "what did X work on last week"); Grep/Glob/Read failed to find the referenced code — this skill searches across repos and systems beyond the current workspace. DO NOT TRIGGER when: you only need current implementation (not history or reasoning) — use Grep/Glob/Read directly.
Semantically searches, greps, and Q&A across codebases indexed in CodeAlive. Can list data sources, read files, trace call graphs, and query artifact metadata.