Skill Claude CodeCodex
Prefer Frigg MCP for indexed source. resulthandle + readmatch for proof.
344 tagged code-intelligence, measured the same way as everything else here.
Browse within: code-search 62local-first 47code-analysis 46code-graph 42knowledge-graph 40ast 39coding-agents 38coding-agent 36ai-coding-agent 32pi-extension 32pi-package 32go 27lsp 27code-index 26
Skill Claude CodeCodex
Prefer Frigg MCP for indexed source. resulthandle + readmatch for proof.
Skill Claude CodeCodex
Query and analyze codebases using the Code Explorer knowledge graph. Use for finding symbols, analyzing impact, understanding architecture, exploring code relationships, generating documentation, and asking questions about code.
Skill Claude CodeCodex
Review maintainability like a principal engineer. Use when the user asks what a senior/staff/principal maintainer would notice, whether code looks vibe-coded, what is gross, what should be fundamentally different, or which architecture smells matter beyond ordinary deduplication.
Skill Claude CodeCodex
Optimize performance scientifically with current scip-query evidence. Use for benchmarking, profiling, cold or warm indexing, command latency, memory and computational cost, or comparing current-pipeline tuning with alternative designs.
Skill Claude CodeCodex
Audit whether implementations are real with scip-query. Use for suspected faked or half-implemented features, decorative checkers or verifiers that never fail, dead code paths hidden behind graceful fallbacks, metrics that may be lying, or a "does any of this actually work" interrogation of a system.
cdeust/ai-architect-mcp-codebase
Skill Claude CodeCodex
Part of ai-architect-mcp-codebase
Trace the structural blast radius of a proposed or actual code change with ai-architect. Use for implementation planning, pull-request review, regression analysis, dependency checks, or identifying callers, importers, users, communities, and processes affected by a symbol or diff.
cdeust/ai-architect-mcp-codebase
Skill Claude CodeCodex
Part of ai-architect-mcp-codebase
Build an evidence-backed map of an unfamiliar repository with the ai-architect code graph. Use before implementing a feature, debugging an unfamiliar subsystem, explaining architecture, or making structural claims about symbols and dependencies.
cdeust/ai-architect-mcp-codebase
Skill Claude CodeCodex
Part of ai-architect-mcp-codebase
Check whether a proposed implementation plan matches the current code graph. Use before coding or approving a plan that names files, symbols, dependencies, boundaries, or expected blast radius; this is structural plan validation, not full PRD or semantic correctness verification.
Skill Claude CodeCodex
Test codeweave-mcp tools against any project using TestHarness. Use this whenever verifying tool behavior, testing a code change, or running custom assertions — e.g. "test the harness", "run tests against X project", "does semanticsearch work correctly".
jarvis-intelligence/jarvis-index
Skill Claude CodeCodex
Part of jarvis
Report bugs and request features for the jarvis MCP server via GitHub issues. Use when jarvis errors, an index fails, a limitation bites, or to request an improvement.
jarvis-intelligence/jarvis-index
Skill Claude CodeCodex
Part of jarvis
Install and configure jarvis, the local-first structural code intelligence. Use when onboarding, running setup.sh, registering the MCP server, or indexing a repo for the first time.
jarvis-intelligence/jarvis-index
Skill Claude CodeCodex
Part of jarvis
Use jarvis structural code intelligence for code structure queries: finding references, go-to-definition, call/type hierarchy, who calls a function, where a symbol is defined, document symbols, natural-language semantic search. Prefer over grep.
Skill Claude CodeCodex
Plan safer refactors with CodeMeridian by checking graph freshness, exact symbols, impact, tests, duplication, and architecture risk before editing.
Skill Claude CodeCodex
Plan focused tests with CodeMeridian by finding relevant test shields, coverage gaps, impacted behavior, and the smallest useful test set before implementation.
Skill Claude CodeCodex
Preserve and strengthen the user's independent reasoning during design, strategy, learning, interpretation, hypothesis work, and consequential decisions, and preserve justified durable context with explicit provenance when supported. Use when a task benefits from human-led judgment, model-building, productive…
Skill Claude CodeCodex
Use when Claude needs project-aware code memory, MCP context retrieval, repository indexing, causal code search, or Droste CLI workflows. Triggers include requests to index a repo with Droste, configure droste mcp, retrieve graph-aware context, inspect caller/callee relationships, avoid blind file reads, or keep…
Skill Claude CodeCodex
Use when the chat should save durable knowledge into Droste-Memory, retrieve spatial memory context, pan or zoom the Droste camera, reveal hidden detail layers, or synchronize with the local FastAPI visualizer.
Skill Claude CodeCodex
Part of codeindex
Answer code questions structurally instead of reading whole files. Use when you need to find where something is defined, read one function, see what calls a symbol, trace imports, judge what a change breaks, or orient yourself in an unfamiliar file or repository. Reach for this before Read, Grep or Glob on a code…
tijuthomas5/context-bridge-mcp
Skill Claude CodeCodex
Copy this file into your project root and rename it to match your AI tool.
Skill Claude CodeCodex
When to use.
Skill Claude CodeCodex
When to use.
Skill Claude CodeCodex
When to use.
Skill Claude CodeCodex
Use Codexa selectively for ambiguous, cross-cutting, or high-risk repository work that needs search, change planning, dependency context, or verification guidance beyond exact source inspection.
Skill Claude CodeCodex
Create a bumpy bump file describing which packages changed and how, for version bumping and changelog generation. Use when the user wants to record a change, add a bump file, or prepare packages for release.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: