Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
WHEN analyzing async/await performance, ValueTask correctness, ConfigureAwait decisions, IO.Pipelines, ThreadPool tuning, or Channel selection in .NET code. WHEN NOT profiling interpretation (use dotnet-performance-analyst) or thread sync bugs (use dotnet-csharp-concurrency-specialist).
Read-only helper that queries Binary Ninja MCP / BinAssistMCP and static-analysis CLIs (radare2, objdump, strings, otool, class-dump) on behalf of the main agent. Spawn this when a static probe will return >1 KB of disassembly, a function decompile, a symbol cross-reference list, or a full S-box / round-constant table…
Use when an OpenClaw instance has a problem the health sentinel couldn't fix — gateway failures, config drift, stuck processes, cron breakage, or when deep diagnosis is needed.
Scans Odoo modules for version compatibility issues and generates structured reports. Use when analyzing modules before upgrade or when the user asks to check module compatibility.
The Performance Analyst profiles application performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory analysis, response time investigation, or optimization strategy.
Deep code understanding expert using AST knowledge graph. Use when exploring unfamiliar code, tracing complex relationships, or understanding module architecture.
Audits your memory directory for orphans, phantom references, index drift, broken wiki-links, stale entries, and near-duplicates. Writes a dated health report. Use on-demand (a monthly cadence works well) once your memory store has grown enough that drift between the index and the files is plausible.
USE WHEN a test intermittently fails on unchanged code. Runs it N times sequentially, captures pass/fail + stderr, groups failures by normalized signature, returns stability report. Read-only — never modifies code or installs deps. For statistical signal across runs, not one-shot diagnosis.
Advisory, non-authoring reviewer of a /debug or /fix hand-off (a Debug Report + needs-verification, or a batch-PR body). Checks that the hypothesis is evidence-backed, the root cause is real (not a symptom), the verification is falsifiable, systemic-patterns was consulted (by-design? regression? shared root?), the fix…
This page documents hard-won lessons from debugging the SolidWorks COM bridge. If you are an AI coding assistant (Claude, GPT-4, Gemini, Copilot, etc.) working on this codebase, read this page before touching any COM-related code. Every entry below caused a real runtime failure that required hours to diagnose.
You are a reverse-engineering expert, your goal is to find stuffs in IDA. You can use the ida-pro-mcp tools to retrieve information. In general use the following strategy.
Debug Java applications using JDB. Use when the user wants to debug Java code, investigate runtime behavior, catch exceptions, inspect variables, collect thread dumps, or diagnose JVM issues.
Collect JVM diagnostics via JDB — thread dumps, deadlock detection, loaded class listings. Use for quick health checks on a running JVM with JDWP enabled without starting a full interactive debugging session.
Run interactive JDB debugging sessions. Use when launching a JVM under JDB, attaching to a running JVM with JDWP, setting breakpoints, stepping through code, inspecting variables, catching exceptions, or navigating call stacks.
Proactively audit the assumption registry for stale, unverified, or newly-broken assumptions. Use on a schedule (weekly) or when starting work that depends on external systems. Unlike dependency-verifier (reactive, investigates on demand), this agent walks the full registry and flags what needs attention.
Expert read-only code review specialist for explicit review/audit requests only. Use for /review, /code-review, explicit code/diff review or audit requests, or when the user directly selects code-reviewer. Do not use automatically after normal coding changes.