From mimirs
Provides semantic search, code navigation, git history queries, conversation memory, checkpoints, and annotations for projects. Useful for finding code, usages, dependencies, and past discussions.
npx claudepluginhub thewinci/mimirs --plugin mimirsThis skill uses the workspace's default tool permissions.
This project has a local RAG index (mimirs). Use these MCP tools proactively:
Performs semantic search, grep, artifact fetching, relationship tracing, and data source listing across CodeAlive-indexed codebases and docs.
Retrieves codebase context via hybrid semantic/lexical search with neural reranking. Guides tool choice for implementations, symbol relationships, patterns, Q&A, and multi-repo queries.
Enables semantic code search, blast-radius analysis for refactors, risk-scored PR reviews, and health audits via local MCP server. Use for large codebases needing deep structural insights.
Share bugs, ideas, or general feedback.
This project has a local RAG index (mimirs). Use these MCP tools proactively:
search: Discover which files are relevant to a topic. Returns file paths
with snippet previews — use this when you need to know where something is.read_relevant: Get the actual content of relevant semantic chunks —
individual functions, classes, or markdown sections — ranked by relevance.
Results include exact line ranges (src/db.ts:42-67) so you can navigate
directly to the edit location. Use this instead of search + Read when
you need the content itself.project_map: When you need to understand how files relate to each other,
generate a dependency graph. Use focus to zoom into a specific file's
neighborhood.search_conversation: Search past conversation history to recall previous
decisions, discussions, and tool outputs. Use this before re-investigating
something that may have been discussed in an earlier session.create_checkpoint: Call this as your final step after completing any
user-requested task, before responding to the user. Also call when hitting
a blocker or changing direction mid-task. Include what was done, which files
changed, and why.list_checkpoints / search_checkpoints: Review or search past
checkpoints to understand project history and prior decisions.index_files: If you've created or modified files and want them searchable,
re-index the project directory.search_analytics: Check what queries return no results or low-relevance
results — this reveals documentation gaps.search_symbols: When you know a symbol name (function, class, type, etc.),
find it directly by name instead of using semantic search.find_usages: Before changing a function or type, find all its call sites.
Use this to understand the blast radius of a rename or API change.git_context: At the start of a session, call this to see what files have
already been modified, recent commits, and which changed files are in the index.search_commits: Semantically search git commit history — find why code
was changed, when decisions were made, or what an author worked on.file_history: Get the commit history for a specific file — returns commits
that touched it, sorted by date.annotate: Call this immediately when you encounter a known bug, race
condition, fragile code, non-obvious constraint, or workaround while reading
code. Notes persist across sessions and surface as [NOTE] blocks inline in
read_relevant results automatically.get_annotations: Retrieve all notes for a file, or search semantically
across all annotations.delete_annotation: Remove an annotation that is no longer relevant — a
fixed bug, a lifted constraint, or a note on deleted code. Use
get_annotations first to find the ID.write_relevant: Before adding new code or docs, find the best insertion
point — returns the most semantically appropriate file and anchor.generate_wiki: Generate or update a structured markdown wiki for the
codebase. Call with run: true to immediately execute all phases. Follow
the returned instructions step by step using the other mimirs tools to
build wiki pages in wiki/.